Skip to main content
Run a tool with its ID and an input that matches its input schema. Each run starts a job, which carries the result when it succeeds.

​
From an MCP client

For a read tool, your agent calls run_read_only_website_tool, with the input as a JSON-encoded string:
The call usually returns the finished job in seconds. If the job is still running, follow its next (get_job with wait_seconds) instead of running the tool again. For a write tool, use run_website_tool and send an idempotency_key.

​
From the REST API

REST answers at once with 202 and the job. Read the job after the Retry-After seconds, until its status is succeeded, failed or cancelled:
Save the result when you read it: it is kept until its first read, and at most 60 minutes after the job ends.
  • Run a write tool with POST /v1/runs and an Idempotency-Key header, so a retry returns the same job instead of acting on the site twice. See retries and idempotency.
  • A job can stop with status needs_input to ask a question, such as a sign-in code. See answer questions.
  • Instead of polling, get a webhook when a job asks a question or finishes.
  • A tool that signs in uses your saved login for the site. See logins.

​
Next

Build a tool when none fits your task.