Integration MCP tools

An integration MCP serves one site’s tools plus get_job, answer_job and cancel_job. Each site tool takes its own input schema, the one find_website_tool returns as input_schema, under input. The example below is an Amazon integration with two tools; yours lists its own.

Site tools (example)

`search_products`

Search Amazon’s catalog by keywords and return up to 20 products with title, price, rating and URL. Returns the validated operation result. A client that accepts SSE gets a stream that waits up to 5 minutes for the result, with progress while the job runs. Any other client waits up to 50 seconds. A run that asks a question returns input_required at once. A job still running then returns status “running” with its job_id; follow its next block (get_job with wait_seconds) instead of calling again. Effect: Reads only; changes nothing.

Argument	Required	Type	Description
`input`	Yes	object	The operation’s input: query (string, required): Words to search for; max_price (integer): Highest price in cents, optional.
`retry_key`	No	string	Optional. Your key for this call; reuse it only to retry the same call.
`connected_account_id`	No	string	Optional. The ID of the saved login to sign in with, when the site has several.
`correct_rejected_credentials`	No	one of: `true`	Optional. Ask to correct this saved login during the run; requires connected_account_id.
`website_auth`	No	object	Optional. A website login for this call, used only when the site has no saved login this caller may use; save stores it. Values passed here are visible to your client and its model provider; the protected form keeps them out of this conversation. Pomerado keeps them from the minting model, traces and logs either way.
`sign_in_method`	No	one of: `sms`, `call`, `email`, `totp`, `push`	The two-factor method (sms, call, email, totp or push) the tool’s sign-in picks when the site offers several. Without it, a saved authenticator seed picks totp, otherwise the run asks.

`get_order_status`

Read the status and delivery estimate of one order from the signed-in Amazon account. Returns the validated operation result. A client that accepts SSE gets a stream that waits up to 5 minutes for the result, with progress while the job runs. Any other client waits up to 50 seconds. A run that asks a question returns input_required at once. A job still running then returns status “running” with its job_id; follow its next block (get_job with wait_seconds) instead of calling again. Signs in with this site’s saved login; pass connected_account_id to choose among several. website_auth is used only when no login is saved, and one that differs from a saved login is refused. Without either, the run asks the user for the login on its protected page and may save it. A job that reports status needs_credentials (the website rejected its saved login; a run waits only when nothing was changed, and a build that may have changed the website checks that on resuming, as possible_commit says) waits up to 60 minutes for the user who started it to correct that login, then resumes as the same job; its next names the page to correct it. Do not resubmit it. Its sign-in takes: email, password; two-factor sign_in_method: sms, authenticator. website_auth may carry the listed ones; one the login lacks is asked for when the sign-in needs it. Effect: Reads only; changes nothing.

Argument	Required	Type	Description
`input`	Yes	object	The operation’s input: order_number (string, required): The order number from the confirmation email.
`retry_key`	No	string	Optional. Your key for this call; reuse it only to retry the same call.
`connected_account_id`	No	string	Optional. The ID of the saved login to sign in with, when the site has several.
`correct_rejected_credentials`	No	one of: `true`	Optional. Ask to correct this saved login during the run; requires connected_account_id.
`website_auth`	No	object	Optional. A website login for this call, used only when the site has no saved login this caller may use; save stores it. Values passed here are visible to your client and its model provider; the protected form keeps them out of this conversation. Pomerado keeps them from the minting model, traces and logs either way.
`sign_in_method`	No	one of: `sms`, `authenticator`	The two-factor method (sms, call, email, totp or push) the tool’s sign-in picks when the site offers several. Without it, a saved authenticator seed picks totp, otherwise the run asks.

Job tools

The Pomerado MCP’s get_job, answer_job and cancel_job, reaching only this integration’s jobs.

​Site tools (example)

​search_products

​get_order_status

​Job tools

Site tools (example)

`search_products`

`get_order_status`

Job tools