Skip to content
Menu

REWALTO / DEVELOPERS / MCP / TOOLS

Rewalto MCP server tools: Task

The Task group of Rewalto's MCP server has 4 tools as of 8 November 2026, 8:53 pm IST. Each tool below shows what it returns, its credit cost, who can call it and its inputs, read live from Rewalto's public tool list.

Task (4 tools)

cancel_task

Cancel a task. Stops a queued or running task: the call in flight is dropped, the rest are skipped, and every result it already has is kept. Free. Needs an API key; answers for the key’s own organisation only.

Credit cost
Free; saves a record
Who can call it
API key or Sign in with Rewalto, permission tools:run
Inputs
  • id (string, required): The task id.

get_task

A task and its results. One task: its state, budget and counts, and every step with every call: its URL, state, attempts, error and its tool’s answer (output). Free. Needs an API key; answers for the key’s own organisation only.

Credit cost
Free
Who can call it
API key or Sign in with Rewalto, permission data:read
Inputs
  • id (string, required): The task id.

list_tasks

Tasks. The organisation’s tasks, newest first: each one’s state, what stopped it and its call counts (no results: read get_task for them). Free. Needs an API key; answers for the key’s own organisation only.

Credit cost
Free
Who can call it
API key or Sign in with Rewalto, permission data:read
Inputs
  • limit (string, optional): At most this many rows (the API caps it).
  • cursor (string, optional): The `next` cursor from the previous page.

run_task

Run several free tools as one task. Runs up to 10 steps in order as one background job; each step is one free tool with that tool’s own arguments: search (as search_web), page (fetch_page), extract (extract_page, by url only), site (read_site), file (read_file) or browser (browse_page). A step can take its URLs from an earlier one: urlsFrom {step, take} makes one call per URL from the first `take` search results, site pages or page links (leave out url then). Answers at once with the task id; read get_task until state is succeeded, partial, failed or cancelled, for every call’s result. Budget: maxSeconds (10 to 900, default 300) and maxCalls (1 to 50, default 25); a task stopped by a bound or cancel keeps what it had. Every call passes its tool’s own guards and counts in its own hourly limit. At most 20 tasks an hour and 3 open at once for your organisation. Free. Needs an API key; answers for the key’s own organisation only.

Credit cost
Free; saves a record
Who can call it
API key or Sign in with Rewalto, permission tools:run
Inputs
  • name (string, optional): Your label for it.
  • steps (list of object, required): In order. Each {id, tool, input, urlsFrom?}: id is your name for the step (lowercase, unique), tool one of search, page, extract, site, file, browser, input that tool’s arguments, urlsFrom {step, take} an earlier step’s id and how many of its URLs (1 to 10).
  • budget (object, optional): Bounds for the whole task.
  • idempotencyKey (string, optional): Optional: your own unique key (8 to 128 letters, digits . _ : -). Sending it again returns the same record instead of a second one. One is made when left out.

How the tools charge

Each tool is one call to the Rewalto API, with the same permissions, credit rates and quote and approval steps as the API, the CLI and the dashboard. Calling the tool list is free and needs no key. A tool marked as spending credits charges only for data delivered, at the published rate, and each answer says what it charged. A run that delivers nothing costs nothing. See pricing and credits and receipts.