Your agent needs to find video — which channels own a topic, which videos rank for a phrase, what exists in a given country and language.
What you can ask for • "Which videos rank for 'rag pipeline tutorial' in the US this month?" • "Find channels publishing about MCP, sorted by relevance." • "What playlists cover this subject in Japanese?" • "Search videos uploaded this week only."
How to use it Point any MCP client at https://mcp.aisa.one/youtube-search/mcp and sign in with OAuth — there is no key to create or paste. One search tool covering videos, channels and playlists, narrowed by country, language, upload date, duration and sort order.
It is also a door to the rest The same login reaches 26 sources and 580+ operations. Find the video here, then ask the same agent what the channel's site traffic is or what the same phrase does in Google — without adding a second server.
What it costs Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident.
Where else it reaches https://mcp.aisa.one/social/mcp for X plus Instagram, Reddit, Pinterest and YouTube; https://mcp.aisa.one/gtm/mcp for those plus Similarweb and Apollo.
Scored across 8 tools
The core pipeline (search → batch_get_schema → batch_quote → batch_use) is reasonably distinct, and account/list_categories are differentiated by descriptions. However, the deprecated `use` tool directly overlaps with `batch_use`, and `search` vs. `list_categories` both serve discovery, creating potential misselection.
All names use snake_case, and the `batch_*` trio is consistent, but conventions are mixed: some tools use `verb_noun` (get_youtube_search, list_categories), some are bare nouns (account), some bare verbs (search, use), and batch_quote is noun-like despite being an action. The pattern is readable but not predictable.
Eight tools is a reasonable count for a router-style server, with each pipeline step earning its place except the deprecated `use` tool, which is dead weight. The set is slightly heavy on platform meta-tools relative to the single YouTube data tool.
The router lifecycle is well covered (discovery, schema, quote, execute, account, categories), but the direct YouTube surface is thin: only search is exposed, with no video detail, channel listing, playlist, or transcript tools. Agents could work around this via batch_use with other published tools, but the server's own surface has notable gaps.
Who am I, what can I use, how much can I spend: the key, the account balance, the Go-to-Market wallet when one is active, and usage for today, 7 days and 30 days. Free; needs the Authorization header. Call it to verify a new connection or to explain a 402. ok is true only when the balance was read; otherwise each entry of errors says what to do in next_step.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Adds substantial context beyond the readOnlyHint/openWorldHint/destructiveHint annotations: the call is free, it requires the Authorization header, and it discloses result semantics ('ok is true only when the balance was read; otherwise each entry of errors says what to do in next_step'). That tells an agent how to interpret partial failure, which annotations cannot convey.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Three sentences, front-loaded with what the agent gets, followed by cost/auth, then call triggers, then result interpretation. No sentence is redundant and none could be dropped without losing information.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read tool with an output schema already present, the description covers the remaining gaps: cost, auth requirement, invocation triggers, and the ok/errors/next_step contract. Nothing an agent needs to call or interpret it correctly is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the description has nothing parameter-level to compensate for, and the schema is fully covered. A 4 rather than 5 reflects that it adds no input-syntax detail, though none is possible here.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description states a concrete resource set (identity/key, account balance, Go-to-Market wallet, usage over 1/7/30 days) rather than restating the name. It is clearly distinguishable from every sibling, which are all Reddit, batch, or search tools. An agent knows exactly what it will learn by calling it.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicit triggering conditions are given: 'Call it to verify a new connection or to explain a 402.' That is a strong when-to-use statement. It stops short of 5 because it names no alternative tool or a when-not condition, though the sibling list offers no obvious competing diagnostic.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Retrieve schemas for 1 to 20 exact tool names from search. Build arguments from successful schemas, then call batch_quote. Do not call batch_use yet. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
| Name | Required | Description | Default |
|---|---|---|---|
| tools | Yes | Exact tool names returned by search whose complete contracts are needed. Never invent tool names. | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. | |
| include_documentation | No | Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support. | |
| include_response_schema | No | Return the complete response_schema. Defaults to false. | |
| include_arguments_schema | No | Return the complete arguments_schema. Defaults to true. |
| Name | Required | Description |
|---|---|---|
| tools | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| error_count | Yes | |
| total_count | Yes | |
| success_count | Yes | |
| next_steps_guidance | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is not required to restate it. It adds genuine operational context: the batch_use prohibition, exact-name/prefix requirements, and session reuse semantics. It does not cover failure handling when names are invalid, keeping it below a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Front-loaded with the core action and size limit, and every sentence carries workflow value. The session_id sentence duplicates the schema's own parameter description, which is minor redundancy rather than bloat.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a read-only batch retrieval tool with an output schema, the description supplies the orchestration context an agent needs (source of names, next steps, session handling) without needing to explain return values. Nothing essential to correct invocation is missing.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description adds real meaning beyond the schema by constraining names to those returned by search and warning against a client prefix such as mcp__aisa__, which is not encoded in the schema.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Retrieve schemas for 1 to 20 exact tool names') and pins the source of those names to search. This clearly separates it from siblings like search (finds tools), batch_quote, and batch_use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly sequences the workflow: build arguments from successful schemas, then call batch_quote, and 'Do not call batch_use yet.' This is an explicit when-to-use and when-not-to-use instruction naming the alternative siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Obtain AIsaServices cost quotes for 1 to 20 published tools without executing them. Same input as batch_use: exact tool names and schema-valid arguments. Never falls back to execution. The response reports auto_execute_eligible and auto_execute_threshold_micros_usd. auto_execute_eligible waives only the extra cost-confirmation step and does not override a user prohibition on execution, a narrower scope, or a tighter budget limit. Quotes are price observations, not authorization grants. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
| Name | Required | Description | Default |
|---|---|---|---|
| calls | Yes | ||
| search_id | No | Optional search correlation identifier returned by search. | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| Name | Required | Description |
|---|---|---|
| results | Yes | |
| batch_id | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| error_count | Yes | |
| total_count | Yes | |
| success_count | Yes | |
| next_steps_guidance | Yes | Deterministic next-step instructions derived from this result. Not an authorization grant. |
| auto_execute_eligible | No | True when the worst-known total of successful USD quotes is at or below auto_execute_threshold_micros_usd. A non-USD successful quote makes the batch ineligible. Present on quote responses. |
| auto_execute_threshold_micros_usd | No | Configured auto-execute threshold in micro-USD. 0 disables automatic execution. Present on quote responses. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well past the readOnly/idempotent annotations by explaining that quotes are price observations rather than authorization grants, and precisely delimiting what auto_execute_eligible does and does not waive (user prohibition, narrower scope, tighter budget). It also guarantees no execution fallback, which is the key behavioral risk for this tool.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Purpose is front-loaded and most sentences carry distinct rules (no fallback, eligibility limits, naming, session reuse). It is on the long side and the argument-shape constraint is stated twice in spirit, but little is truly wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
An output schema exists, so return-value documentation isn't required, yet the description still flags the two response fields that matter for a downstream decision. Combined with session and naming guidance, an agent has everything needed to call it correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
At 67% schema coverage the schema already documents each parameter, so the description earns credit only for added meaning: exact-name rules for 'tool', session_id reuse semantics, and the 1-to-20 argument-shape parallel with batch_use. It doesn't clarify search_id beyond what the schema states.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb and resource ('Obtain AIsaServices cost quotes for 1 to 20 published tools') plus the crucial scope qualifier 'without executing them.' It is immediately distinguishable from the sibling batch_use, which executes rather than quotes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Explicitly names the parallel sibling ('Same input as batch_use') and draws the boundary ('Never falls back to execution'). It also gives operational conditions: use names exactly as search returns them, strip any mcp__aisa__ prefix, and reuse session_id from Search for the task.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Billable API calls can incur substantial charges. Never call before a successful batch_quote for the same tools and arguments. Execute only when that quote response reports auto_execute_eligible=true for these calls, or when explicit user authorization covers that cost and risk. auto_execute_eligible waives only the extra cost-confirmation step; it does not override a user prohibition on execution, a narrower scope, or a tighter budget limit. Re-quote if tools, arguments, or scope change. Execute 1 to 20 independent published-tool calls; never silently retry. A missing or failed quote is not free. Use tool names exactly as search returns them, without a client prefix such as mcp__aisa__. Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.
| Name | Required | Description | Default |
|---|---|---|---|
| calls | Yes | ||
| search_id | No | Optional search correlation identifier returned by search. | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| Name | Required | Description |
|---|---|---|
| results | Yes | |
| batch_id | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| error_count | Yes | |
| total_count | Yes | |
| success_count | Yes | |
| next_steps_guidance | Yes | Deterministic next-step instructions derived from this result. Not an authorization grant. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover mutability, destructiveness, and open-world behavior. The description adds critical business logic: billable calls, quote dependency, the meaning of auto_execute_eligible (waives only cost confirmation, not user prohibitions), and no silent retry. It doesn't detail rate limits or return format, but with an output schema present, that's acceptable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is dense and front-loads the cost warning, but it packs many separate instructions into one block, making it less scannable. Some sentences like 'A missing or failed quote is not free' add value, but the overall flow could be better structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the destructive, open-world annotations and the presence of an output schema, the description covers the essential preconditions and behavioral constraints. It could mention error handling or partial failure behavior, but the core guidance is sufficient for correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 67%, and the description adds important semantics: tool names must be exact without client prefix, session_id reuse guidance, and 1-20 call limit. It doesn't explain search_id, but the schema description for search_id is already clear enough.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb and resource: 'Execute 1 to 20 independent published-tool calls', and the title matches. It distinguishes itself from batch_quote by requiring a quote first, but doesn't explicitly contrast with the singular 'use' sibling, though that's implied by 'batch'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives explicit when-to-use and when-not-to-use conditions: only after a successful batch_quote with auto_execute_eligible=true or explicit user authorization. It also states re-quote conditions and prohibits silent retries, leaving little ambiguity.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Search YouTube and get back matching videos, channels, and playlists. Set engine=youtube and pass the query in q; both are required. Optionally narrow by country (gl) and interface language (hl), or pass a YouTube filter token in sp for pagination and advanced filters such as upload date, duration, or result type. Use this to find video content on a topic, track a channel's recent uploads, or gauge how much video coverage a subject has. Note: this is served through the AIsa mapped path /apis/v1/youtube/search; the upstream provider's canonical path is not mounted directly.
Published reference price: $0.0029 USD per successful request. Account-specific pricing and final settlement may differ.
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query. Required by runtime and upstream SearchApi. | |
| gl | No | Country code (e.g. us, jp) | |
| hl | No | Interface language | |
| sp | No | YouTube filter token (pagination or advanced filters) | |
| engine | Yes | SearchApi engine identifier. Use `youtube` for this YouTube endpoint. |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description usefully adds pricing ($0.0029 per successful request) and a routing note about the mapped path versus the upstream canonical path, which is real operational context beyond the annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The core capability and required-parameter guidance are front-loaded, and the optional-parameter detail follows logically. The pricing comment block and path-mapping note add length that is only marginally actionable, slightly diluting an otherwise tight description.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, rich annotations, and full schema description coverage, the description supplies exactly the missing pieces: required params, filter-token semantics, cost, and endpoint routing. Nothing an agent needs to invoke this correctly is absent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so the baseline is 3. The description goes further by clarifying that engine and q are both required, that sp carries pagination and advanced filter tokens (upload date, duration, result type), and that gl/hl narrow by country and interface language.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource ('Search YouTube') and enumerates the returned entities (videos, channels, playlists), which an agent can act on immediately. It does not explicitly contrast itself with the sibling 'search' tool, so the distinction is implied rather than stated.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Gives three concrete use cases (topic discovery, tracking a channel's uploads, gauging coverage) plus the mandatory engine/q pairing. There are no when-not-to-use conditions or named alternatives among the siblings, which keeps it out of 5 territory.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
The AIsa catalogue at a glance: categories, the servers in each, tool counts, and the dedicated endpoint to connect if you only need one category. Free. (AIsa-only: tool-router has no equivalent.) Use mcp.aisa.one/mcp?modules=<category> (or mcp.aisa.one/<category>/mcp) to have that category's tools listed directly instead of via search.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish that this is a safe, read-only, closed-world operation. The description adds useful context beyond annotations by saying it returns categories, servers, tool counts, and the dedicated endpoint, and that it is free. It omits auth/rate-limit details, but those are less critical given the read-only annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is front-loaded with what the tool returns and is generally efficient. The parenthetical about tool-router and the endpoint URL add some density, but each part contributes usage or content context.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With zero parameters, read-only annotations, and an output schema available, the description supplies enough context for correct invocation. It explains the catalogue contents and gives the category-specific endpoint alternative, leaving no critical gap for an agent.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so parameter semantics are not a meaningful differentiator. The schema has no properties to explain, and the description does not need to document any inputs.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states that this tool gives a catalogue overview: categories, servers per category, tool counts, and a dedicated endpoint. The resource is specific and recognizable, though sibling differentiation is only partial because it references 'tool-router' rather than the listed siblings like search/use.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives a clear alternative: use the category-specific endpoint if you only need one category, rather than going via search. It also notes the tool is free and AIsa-only, but it does not explicitly state when to call list_categories instead of search or use.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Discover AIsa tools and Plans for external data or actions. Skip tasks that only need supplied content or general knowledge. For multi-step tasks, search the full goal before decomposing it. Use English; put identifiers in known_fields. If has_full_schema=false, call batch_get_schema. Next call batch_quote, not batch_use. Do not search for standalone rewriting, translation, summarization, formatting, or calculations on supplied content. For one capability, use an atomic query. Select a matching capability, date window, and metric. A Plan may cover only part of the task; assess its purpose and follow next_steps_guidance.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum number of additional direct tool candidates. | |
| query | Yes | Natural-language capability or task to discover. | |
| category | No | Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.) | |
| session_id | No | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. | |
| known_fields | No | Known values such as ticker, URL, provider, or identifier that improve retrieval. | |
| provider_filters | No | Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown. |
| Name | Required | Description |
|---|---|---|
| plan | No | |
| tools | Yes | |
| search_id | Yes | |
| session_id | Yes | Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created. |
| retrieval_mode | No | |
| next_steps_guidance | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds workflow behavior the annotations cannot: the has_full_schema flag gates a required batch_get_schema call, and the next step after search is batch_quote, not batch_use. It stops short of disclosing retrieval limits or catalog breadth that would push it to a 5.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a dense run of imperatives rather than flowing prose, but each sentence carries a distinct rule (scope, language, workflow branch, negative cases, result interpretation) and the most important scoping guidance is front-loaded. Slightly more compression would help.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With an output schema present, the description need not explain return values, and it correctly avoids doing so while still referencing the output fields that drive the workflow (has_full_schema, next_steps_guidance). A mutation-free, well-annotated search tool is adequately covered, though catalog scope ('AIsa-only', no external providers) could be stated more explicitly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the structured baseline is 3. The description adds genuine meaning beyond the schema by telling the agent to write the query in English and to place tickers, URLs, providers, or identifiers in known_fields, which is non-obvious routing guidance for a nested free-form object.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description opens with a specific verb+resource: 'Discover AIsa tools and Plans for external data or actions.' It also separates this discovery step from the sibling execution tools by naming batch_get_schema, batch_quote, and batch_use and stating when each follows, so an agent can place it in the workflow without opening schemas.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It gives explicit when-to-use ('tasks needing external data or actions'), when-not ('tasks that only need supplied content or general knowledge'; no standalone rewriting, translation, summarization, formatting, or calculations), and named alternatives (batch_get_schema when has_full_schema=false, batch_quote rather than batch_use). It also specifies query language and atomic-query style, leaving little to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
deprecated, use batch_use instead
| Name | Required | Description | Default |
|---|---|---|---|
| arguments | No | Arguments matching input_schema / arguments_schema | |
| search_id | No | search_id from the search that found this operation | |
| operation_id | Yes | operation_id as returned by search | |
| max_price_usd | No | Refuse the call before any spend if its quoted price is above this many USD |
| Name | Required | Description |
|---|---|---|
No output parameters | ||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the agent knows this is a state-changing, open-world operation. The description adds only the deprecation status and says nothing about what gets mutated, spend behavior (despite a max_price_usd param), or authorization needs.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single clause with zero waste; the deprecation notice and the replacement are front-loaded. It is terse by design for a deprecated endpoint, though it is under-specified rather than optimally efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Has an output schema and annotations, which reduces the burden, but a 4-parameter operation tool with a deprecation notice gives no information about what it executes or whether it remains functional. For an agent deciding between this and batch_use, the description is thin.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so all four parameters (operation_id, arguments, search_id, max_price_usd) are already documented in the schema. The description adds no parameter meaning on top, so the baseline 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description never states what the tool does — no verb or resource. It only labels the tool as deprecated and points to a replacement, leaving the actual capability ('Run an AIsa operation' from the title) unexplained. An agent must infer the purpose from the title and schema alone.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
It explicitly routes the agent to the alternative ('use batch_use instead'), which is exactly the guidance needed for a deprecated tool. It doesn't explain when, if ever, this tool should still be called (e.g., during a migration window), so it stops short of a 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
accountget_detailsbatch_get_schemabatch_quotebatch_use18 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / descriptionRemoved value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"Input schema / properties / calls / items / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / items / additionalPropertiesPrevious value: -trueNew value: +falseInput schema / properties / calls / items / propertiesAdded value: +{
+ "arguments": {
+ "additionalProperties": true,
+ "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.",
+ "type": "object"
+ },
+ "call_id": {
+ "description": "Caller-chosen identifier unique within this batch.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+ },
+ "tool": {
+ "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.",
+ "minLength": 1,
+ "type": "string"
+ }
+}Input schema / properties / calls / items / requiredAdded value: +[
+ "call_id",
+ "tool",
+ "arguments"
+]Input schema / properties / calls / maxItemsAdded value: +20Input schema / properties / calls / minItemsAdded value: +1Input schema / properties / max_price_usdRemoved value: -{
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Per-call price cap applied to every item"
-}Input schema / properties / search_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / search_id / defaultRemoved value: -nullInput schema / properties / search_id / descriptionPrevious value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search."Input schema / properties / search_id / typeAdded value: +"string"Input schema / properties / session_idAdded value: +{
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+}Output schema / $defsAdded value: +{
+ "jsonValue": {
+ "anyOf": [
+ {
+ "additionalProperties": {
+ "$ref": "#/$defs/jsonValue"
+ },
+ "type": "object"
+ },
+ {
+ "items": {
+ "$ref": "#/$defs/jsonValue"
+ },
+ "type": "array"
+ },
+ {
+ "type": "string"
+ },
+ {
+ "type": "number"
+ },
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "JSON value returned by the upstream tool."
+ }
+}Output schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Output schema / propertiesAdded value: +{
+ "batch_id": {
+ "type": "string"
+ },
+ "error_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "next_steps_guidance": {
+ "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "results": {
+ "items": {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "call_id": {
+ "type": "string"
+ },
+ "customer_cost_micros_usd": {
+ "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.",
+ "minimum": 0,
+ "type": "integer"
+ },
+ "data": {
+ "$ref": "#/$defs/jsonValue"
+ },
+ "error": {
+ "anyOf": [
+ {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "retryable": {
+ "type": "boolean"
+ },
+ "status": {
+ "type": "integer"
+ },
+ "type": {
+ "enum": [
+ "validation",
+ "authentication",
+ "payment",
+ "permission",
+ "rate_limit",
+ "upstream",
+ "timeout",
+ "internal"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "status",
+ "retryable"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "request_id": {
+ "type": "string"
+ },
+ "successful": {
+ "type": "boolean"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "upstream_status": {
+ "description": "HTTP status returned by AIsaServices when a request was dispatched.",
+ "type": "integer"
+ }
+ },
+ "required": [
+ "call_id",
+ "tool",
+ "successful",
+ "request_id"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "session_id": {
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "minLength": 1,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+ },
+ "success_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "total_count": {
+ "minimum": 1,
+ "type": "integer"
+ }
+}Output schema / requiredAdded value: +[
+ "session_id",
+ "batch_id",
+ "total_count",
+ "success_count",
+ "error_count",
+ "results",
+ "next_steps_guidance"
+]get_details13 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / argumentsRemoved value: -{
- "anyOf": [
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them."
-}Input schema / properties / include_arguments_schemaAdded value: +{
+ "default": true,
+ "description": "Return the complete arguments_schema. Defaults to true.",
+ "type": "boolean"
+}Input schema / properties / include_documentation / descriptionPrevious value: -"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."New value: +"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."Input schema / properties / include_response_schemaAdded value: +{
+ "default": false,
+ "description": "Return the complete response_schema. Defaults to false.",
+ "type": "boolean"
+}Input schema / properties / operation_idRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "One operation_id from search"
-}Input schema / properties / operation_idsRemoved value: -{
- "anyOf": [
- {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Up to 20 operation_ids, for a batch"
-}Input schema / properties / session_idAdded value: +{
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+}Input schema / properties / toolsAdded value: +{
+ "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.",
+ "items": {
+ "minLength": 1,
+ "pattern": "^\\S(?:.*\\S)?$",
+ "type": "string"
+ },
+ "maxItems": 20,
+ "minItems": 1,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / with_quoteRemoved value: -{
- "default": true,
- "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.",
- "type": "boolean"
-}Input schema / requiredAdded value: +[
+ "tools"
+]Output schema / propertiesAdded value: +{
+ "error_count": {
+ "type": "integer"
+ },
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "session_id": {
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "minLength": 1,
+ "pattern": "^[A-Za-z0-9_-]{1,128}$",
+ "type": "string"
+ },
+ "success_count": {
+ "type": "integer"
+ },
+ "tools": {
+ "additionalProperties": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "canonical_operation_id": {
+ "type": "string"
+ },
+ "documentation": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "error": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ]
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "idempotent": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "read_only": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "response_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "side_effects": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "successful": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "successful"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "total_count": {
+ "type": "integer"
+ }
+}Output schema / requiredAdded value: +[
+ "error_count",
+ "next_steps_guidance",
+ "session_id",
+ "success_count",
+ "tools",
+ "total_count"
+]search17 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / category / anyOfRemoved value: -[
- {
- "enum": [
- "seo",
- "finance",
- "social",
- "search",
- "sales",
- "mail"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / category / defaultRemoved value: -nullInput schema / properties / category / descriptionPrevious value: -"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."New value: +"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"Input schema / properties / category / enumAdded value: +[
+ "seo",
+ "finance",
+ "social",
+ "search",
+ "sales",
+ "mail"
+]Input schema / properties / category / typeAdded value: +"string"Input schema / properties / known_fieldsAdded value: +{
+ "additionalProperties": true,
+ "default": {},
+ "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.",
+ "type": "object"
+}Input schema / properties / limit / descriptionPrevious value: -"Maximum candidates, 1-10"New value: +"Maximum number of additional direct tool candidates."Input schema / properties / limit / maximumAdded value: +20Input schema / properties / limit / minimumAdded value: +1Input schema / properties / provider_filtersAdded value: +{
+ "default": [],
+ "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.",
+ "items": {
+ "type": "string"
+ },
+ "maxItems": 50,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / query / descriptionPrevious value: -"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."New value: +"Natural-language capability or task to discover."Input schema / properties / query / maxLengthAdded value: +2000Input schema / properties / query / minLengthAdded value: +1Input schema / properties / session_idAdded value: +{
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+}Output schema / propertiesAdded value: +{
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "canonical_use_case": {
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan_ref": {
+ "type": "string"
+ },
+ "primary_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "recommended_steps": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "related_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ },
+ "required": [
+ "canonical_use_case",
+ "description",
+ "known_pitfalls",
+ "plan_ref",
+ "primary_tools",
+ "recommended_steps",
+ "related_tools"
+ ]
+ },
+ "retrieval_mode": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "string"
+ }
+ ]
+ },
+ "search_id": {
+ "type": "string"
+ },
+ "session_id": {
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "minLength": 1,
+ "pattern": "^[A-Za-z0-9_-]{1,128}$",
+ "type": "string"
+ },
+ "tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "description": {
+ "type": "string"
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "has_full_schema": {
+ "type": "boolean"
+ },
+ "match_reasons": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "price": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "retrieval_debug": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "fused_rank": {
+ "type": "integer"
+ },
+ "fused_score": {
+ "type": "number"
+ },
+ "lexical_rank": {
+ "type": "integer"
+ },
+ "lexical_score": {
+ "type": "number"
+ },
+ "rerank_admission_rank": {
+ "type": "integer"
+ },
+ "rerank_rank": {
+ "type": "integer"
+ },
+ "rerank_score": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "number"
+ }
+ ]
+ },
+ "runtime_availability": {
+ "type": "string"
+ },
+ "vector_view_ranks": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "vector_view_scores": {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ }
+ },
+ "required": [
+ "fused_rank",
+ "fused_score",
+ "lexical_rank",
+ "lexical_score",
+ "rerank_admission_rank",
+ "rerank_rank",
+ "runtime_availability",
+ "vector_view_ranks",
+ "vector_view_scores"
+ ]
+ },
+ "summary": {
+ "type": "string"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "description",
+ "has_full_schema",
+ "price",
+ "summary",
+ "tool"
+ ],
+ "type": "object"
+ }
+ }
+}Output schema / requiredAdded value: +[
+ "next_steps_guidance",
+ "search_id",
+ "session_id",
+ "tools"
+]use1 field changedInput schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if it would cost more than this many USD"New value: +"Refuse the call before any spend if its quoted price is above this many USD"batch_get_schemabatch_quotebatch_use18 fields changedInput schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / descriptionAdded value: +"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"Input schema / properties / calls / items / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / items / additionalPropertiesPrevious value: -falseNew value: +trueInput schema / properties / calls / items / propertiesRemoved value: -{
- "arguments": {
- "additionalProperties": true,
- "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.",
- "type": "object"
- },
- "call_id": {
- "description": "Caller-chosen identifier unique within this batch.",
- "maxLength": 128,
- "minLength": 1,
- "type": "string"
- },
- "tool": {
- "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.",
- "minLength": 1,
- "type": "string"
- }
-}Input schema / properties / calls / items / requiredRemoved value: -[
- "call_id",
- "tool",
- "arguments"
-]Input schema / properties / calls / maxItemsRemoved value: -20Input schema / properties / calls / minItemsRemoved value: -1Input schema / properties / max_price_usdAdded value: +{
+ "anyOf": [
+ {
+ "type": "number"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Per-call price cap applied to every item"
+}Input schema / properties / search_id / anyOfAdded value: +[
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / search_id / defaultAdded value: +nullInput schema / properties / search_id / descriptionPrevious value: -"Optional search correlation identifier returned by search."New value: +"search_id from the search that found these operations"Input schema / properties / search_id / typeRemoved value: -"string"Input schema / properties / session_idRemoved value: -{
- "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
- "maxLength": 128,
- "pattern": "^[A-Za-z0-9_-]*$",
- "type": "string"
-}Output schema / $defsRemoved value: -{
- "jsonValue": {
- "anyOf": [
- {
- "additionalProperties": {
- "$ref": "#/$defs/jsonValue"
- },
- "type": "object"
- },
- {
- "items": {
- "$ref": "#/$defs/jsonValue"
- },
- "type": "array"
- },
- {
- "type": "string"
- },
- {
- "type": "number"
- },
- {
- "type": "boolean"
- },
- {
- "type": "null"
- }
- ],
- "description": "JSON value returned by the upstream tool."
- }
-}Output schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Output schema / propertiesRemoved value: -{
- "batch_id": {
- "type": "string"
- },
- "error_count": {
- "minimum": 0,
- "type": "integer"
- },
- "next_steps_guidance": {
- "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.",
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "results": {
- "items": {
- "$schema": "https://json-schema.org/draft/2020-12/schema",
- "additionalProperties": false,
- "properties": {
- "call_id": {
- "type": "string"
- },
- "customer_cost_micros_usd": {
- "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.",
- "minimum": 0,
- "type": "integer"
- },
- "data": {
- "$ref": "#/$defs/jsonValue"
- },
- "error": {
- "anyOf": [
- {
- "$schema": "https://json-schema.org/draft/2020-12/schema",
- "additionalProperties": false,
- "properties": {
- "message": {
- "type": "string"
- },
- "retryable": {
- "type": "boolean"
- },
- "status": {
- "type": "integer"
- },
- "type": {
- "enum": [
- "validation",
- "authentication",
- "payment",
- "permission",
- "rate_limit",
- "upstream",
- "timeout",
- "internal"
- ],
- "type": "string"
- }
- },
- "required": [
- "type",
- "status",
- "retryable"
- ],
- "type": "object"
- },
- {
- "type": "null"
- }
- ]
- },
- "request_id": {
- "type": "string"
- },
- "successful": {
- "type": "boolean"
- },
- "tool": {
- "type": "string"
- },
- "upstream_status": {
- "description": "HTTP status returned by AIsaServices when a request was dispatched.",
- "type": "integer"
- }
- },
- "required": [
- "call_id",
- "tool",
- "successful",
- "request_id"
- ],
- "type": "object"
- },
- "type": "array"
- },
- "session_id": {
- "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
- "maxLength": 128,
- "minLength": 1,
- "pattern": "^[A-Za-z0-9_-]*$",
- "type": "string"
- },
- "success_count": {
- "minimum": 0,
- "type": "integer"
- },
- "total_count": {
- "minimum": 1,
- "type": "integer"
- }
-}Output schema / requiredRemoved value: -[
- "session_id",
- "batch_id",
- "total_count",
- "success_count",
- "error_count",
- "results",
- "next_steps_guidance"
-]get_details13 fields changedInput schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / argumentsAdded value: +{
+ "anyOf": [
+ {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them."
+}Input schema / properties / include_arguments_schemaRemoved value: -{
- "default": true,
- "description": "Return the complete arguments_schema. Defaults to true.",
- "type": "boolean"
-}Input schema / properties / include_documentation / descriptionPrevious value: -"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."New value: +"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."Input schema / properties / include_response_schemaRemoved value: -{
- "default": false,
- "description": "Return the complete response_schema. Defaults to false.",
- "type": "boolean"
-}Input schema / properties / operation_idAdded value: +{
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "One operation_id from search"
+}Input schema / properties / operation_idsAdded value: +{
+ "anyOf": [
+ {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "default": null,
+ "description": "Up to 20 operation_ids, for a batch"
+}Input schema / properties / session_idRemoved value: -{
- "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
- "maxLength": 128,
- "pattern": "^[A-Za-z0-9_-]*$",
- "type": "string"
-}Input schema / properties / toolsRemoved value: -{
- "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.",
- "items": {
- "minLength": 1,
- "pattern": "^\\S(?:.*\\S)?$",
- "type": "string"
- },
- "maxItems": 20,
- "minItems": 1,
- "type": "array",
- "uniqueItems": true
-}Input schema / properties / with_quoteAdded value: +{
+ "default": true,
+ "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.",
+ "type": "boolean"
+}Input schema / requiredRemoved value: -[
- "tools"
-]Output schema / propertiesRemoved value: -{
- "error_count": {
- "type": "integer"
- },
- "next_steps_guidance": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "session_id": {
- "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
- "maxLength": 128,
- "minLength": 1,
- "pattern": "^[A-Za-z0-9_-]{1,128}$",
- "type": "string"
- },
- "success_count": {
- "type": "integer"
- },
- "tools": {
- "additionalProperties": {
- "additionalProperties": false,
- "properties": {
- "arguments_schema": {
- "additionalProperties": true,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ]
- },
- "canonical_operation_id": {
- "type": "string"
- },
- "documentation": {
- "additionalProperties": true,
- "type": "object"
- },
- "error": {
- "additionalProperties": false,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ],
- "properties": {
- "code": {
- "type": "string"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ]
- },
- "execution_supported": {
- "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
- "type": "boolean"
- },
- "execution_unsupported_reason": {
- "description": "Why execution and quoting remain unavailable through this router.",
- "type": "string"
- },
- "idempotent": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "boolean"
- }
- ]
- },
- "known_pitfalls": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "read_only": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "boolean"
- }
- ]
- },
- "response_schema": {
- "additionalProperties": true,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ]
- },
- "side_effects": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "successful": {
- "type": "boolean"
- }
- },
- "required": [
- "successful"
- ],
- "type": "object"
- },
- "type": "object"
- },
- "total_count": {
- "type": "integer"
- }
-}Output schema / requiredRemoved value: -[
- "error_count",
- "next_steps_guidance",
- "session_id",
- "success_count",
- "tools",
- "total_count"
-]search17 fields changedInput schema / $schemaRemoved value: -"https://json-schema.org/draft/2020-12/schema"Input schema / properties / category / anyOfAdded value: +[
+ {
+ "enum": [
+ "seo",
+ "finance",
+ "social",
+ "search",
+ "sales",
+ "mail"
+ ],
+ "type": "string"
+ },
+ {
+ "type": "null"
+ }
+]Input schema / properties / category / defaultAdded value: +nullInput schema / properties / category / descriptionPrevious value: -"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"New value: +"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."Input schema / properties / category / enumRemoved value: -[
- "seo",
- "finance",
- "social",
- "search",
- "sales",
- "mail"
-]Input schema / properties / category / typeRemoved value: -"string"Input schema / properties / known_fieldsRemoved value: -{
- "additionalProperties": true,
- "default": {},
- "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.",
- "type": "object"
-}Input schema / properties / limit / descriptionPrevious value: -"Maximum number of additional direct tool candidates."New value: +"Maximum candidates, 1-10"Input schema / properties / limit / maximumRemoved value: -20Input schema / properties / limit / minimumRemoved value: -1Input schema / properties / provider_filtersRemoved value: -{
- "default": [],
- "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.",
- "items": {
- "type": "string"
- },
- "maxItems": 50,
- "type": "array",
- "uniqueItems": true
-}Input schema / properties / query / descriptionPrevious value: -"Natural-language capability or task to discover."New value: +"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."Input schema / properties / query / maxLengthRemoved value: -2000Input schema / properties / query / minLengthRemoved value: -1Input schema / properties / session_idRemoved value: -{
- "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
- "maxLength": 128,
- "pattern": "^[A-Za-z0-9_-]*$",
- "type": "string"
-}Output schema / propertiesRemoved value: -{
- "next_steps_guidance": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "plan": {
- "additionalProperties": false,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ],
- "properties": {
- "canonical_use_case": {
- "type": "string"
- },
- "description": {
- "type": "string"
- },
- "known_pitfalls": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "plan_ref": {
- "type": "string"
- },
- "primary_tools": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "recommended_steps": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "related_tools": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- }
- },
- "required": [
- "canonical_use_case",
- "description",
- "known_pitfalls",
- "plan_ref",
- "primary_tools",
- "recommended_steps",
- "related_tools"
- ]
- },
- "retrieval_mode": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "string"
- }
- ]
- },
- "search_id": {
- "type": "string"
- },
- "session_id": {
- "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
- "maxLength": 128,
- "minLength": 1,
- "pattern": "^[A-Za-z0-9_-]{1,128}$",
- "type": "string"
- },
- "tools": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "additionalProperties": false,
- "properties": {
- "arguments_schema": {
- "additionalProperties": true,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ]
- },
- "description": {
- "type": "string"
- },
- "execution_supported": {
- "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
- "type": "boolean"
- },
- "execution_unsupported_reason": {
- "description": "Why execution and quoting remain unavailable through this router.",
- "type": "string"
- },
- "has_full_schema": {
- "type": "boolean"
- },
- "match_reasons": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "array"
- }
- ],
- "items": {
- "type": "string"
- }
- },
- "price": {
- "additionalProperties": true,
- "type": "object"
- },
- "retrieval_debug": {
- "additionalProperties": false,
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "object"
- }
- ],
- "properties": {
- "fused_rank": {
- "type": "integer"
- },
- "fused_score": {
- "type": "number"
- },
- "lexical_rank": {
- "type": "integer"
- },
- "lexical_score": {
- "type": "number"
- },
- "rerank_admission_rank": {
- "type": "integer"
- },
- "rerank_rank": {
- "type": "integer"
- },
- "rerank_score": {
- "anyOf": [
- {
- "type": "null"
- },
- {
- "type": "number"
- }
- ]
- },
- "runtime_availability": {
- "type": "string"
- },
- "vector_view_ranks": {
- "additionalProperties": {
- "type": "integer"
- },
- "type": "object"
- },
- "vector_view_scores": {
- "additionalProperties": {
- "type": "number"
- },
- "type": "object"
- }
- },
- "required": [
- "fused_rank",
- "fused_score",
- "lexical_rank",
- "lexical_score",
- "rerank_admission_rank",
- "rerank_rank",
- "runtime_availability",
- "vector_view_ranks",
- "vector_view_scores"
- ]
- },
- "summary": {
- "type": "string"
- },
- "tool": {
- "type": "string"
- }
- },
- "required": [
- "description",
- "has_full_schema",
- "price",
- "summary",
- "tool"
- ],
- "type": "object"
- }
- }
-}Output schema / requiredRemoved value: -[
- "next_steps_guidance",
- "search_id",
- "session_id",
- "tools"
-]use1 field changedInput schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if its quoted price is above this many USD"New value: +"Refuse the call before any spend if it would cost more than this many USD"batch_get_schemabatch_quotebatch_use18 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / descriptionRemoved value: -"Up to 20 items of {call_id, operation_id, arguments}; steps at the same execution_level of a plan go in one batch"Input schema / properties / calls / items / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / calls / items / additionalPropertiesPrevious value: -trueNew value: +falseInput schema / properties / calls / items / propertiesAdded value: +{
+ "arguments": {
+ "additionalProperties": true,
+ "description": "Strictly schema-compliant arguments using the exact field names and types from this tool's arguments_schema.",
+ "type": "object"
+ },
+ "call_id": {
+ "description": "Caller-chosen identifier unique within this batch.",
+ "maxLength": 128,
+ "minLength": 1,
+ "type": "string"
+ },
+ "tool": {
+ "description": "Exact tool name returned by search or batch_get_schema. Never invent a name.",
+ "minLength": 1,
+ "type": "string"
+ }
+}Input schema / properties / calls / items / requiredAdded value: +[
+ "call_id",
+ "tool",
+ "arguments"
+]Input schema / properties / calls / maxItemsAdded value: +20Input schema / properties / calls / minItemsAdded value: +1Input schema / properties / max_price_usdRemoved value: -{
- "anyOf": [
- {
- "type": "number"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Per-call price cap applied to every item"
-}Input schema / properties / search_id / anyOfRemoved value: -[
- {
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / search_id / defaultRemoved value: -nullInput schema / properties / search_id / descriptionPrevious value: -"search_id from the search that found these operations"New value: +"Optional search correlation identifier returned by search."Input schema / properties / search_id / typeAdded value: +"string"Input schema / properties / session_idAdded value: +{
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+}Output schema / $defsAdded value: +{
+ "jsonValue": {
+ "anyOf": [
+ {
+ "additionalProperties": {
+ "$ref": "#/$defs/jsonValue"
+ },
+ "type": "object"
+ },
+ {
+ "items": {
+ "$ref": "#/$defs/jsonValue"
+ },
+ "type": "array"
+ },
+ {
+ "type": "string"
+ },
+ {
+ "type": "number"
+ },
+ {
+ "type": "boolean"
+ },
+ {
+ "type": "null"
+ }
+ ],
+ "description": "JSON value returned by the upstream tool."
+ }
+}Output schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Output schema / propertiesAdded value: +{
+ "batch_id": {
+ "type": "string"
+ },
+ "error_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "next_steps_guidance": {
+ "description": "Deterministic next-step instructions derived from this result. Not an authorization grant.",
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "results": {
+ "items": {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "call_id": {
+ "type": "string"
+ },
+ "customer_cost_micros_usd": {
+ "description": "Actual customer charge settled by AIsaServices, in micro-USD. Omitted when the upstream response does not report it.",
+ "minimum": 0,
+ "type": "integer"
+ },
+ "data": {
+ "$ref": "#/$defs/jsonValue"
+ },
+ "error": {
+ "anyOf": [
+ {
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "additionalProperties": false,
+ "properties": {
+ "message": {
+ "type": "string"
+ },
+ "retryable": {
+ "type": "boolean"
+ },
+ "status": {
+ "type": "integer"
+ },
+ "type": {
+ "enum": [
+ "validation",
+ "authentication",
+ "payment",
+ "permission",
+ "rate_limit",
+ "upstream",
+ "timeout",
+ "internal"
+ ],
+ "type": "string"
+ }
+ },
+ "required": [
+ "type",
+ "status",
+ "retryable"
+ ],
+ "type": "object"
+ },
+ {
+ "type": "null"
+ }
+ ]
+ },
+ "request_id": {
+ "type": "string"
+ },
+ "successful": {
+ "type": "boolean"
+ },
+ "tool": {
+ "type": "string"
+ },
+ "upstream_status": {
+ "description": "HTTP status returned by AIsaServices when a request was dispatched.",
+ "type": "integer"
+ }
+ },
+ "required": [
+ "call_id",
+ "tool",
+ "successful",
+ "request_id"
+ ],
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "session_id": {
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "minLength": 1,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+ },
+ "success_count": {
+ "minimum": 0,
+ "type": "integer"
+ },
+ "total_count": {
+ "minimum": 1,
+ "type": "integer"
+ }
+}Output schema / requiredAdded value: +[
+ "session_id",
+ "batch_id",
+ "total_count",
+ "success_count",
+ "error_count",
+ "results",
+ "next_steps_guidance"
+]get_details13 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / argumentsRemoved value: -{
- "anyOf": [
- {
- "additionalProperties": true,
- "type": "object"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "The arguments the operation would be called with, for a price that reflects them. Keyed by operation_id for a batch, or passed flat for a single operation_id. Routes whose required parameters are validated before pricing have no price without them."
-}Input schema / properties / include_arguments_schemaAdded value: +{
+ "default": true,
+ "description": "Return the complete arguments_schema. Defaults to true.",
+ "type": "boolean"
+}Input schema / properties / include_documentation / descriptionPrevious value: -"Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged."New value: +"Return the complete immutable public OpenAPI operation, referenced declarations, provenance and scoped completeness. Documentation does not change execution support."Input schema / properties / include_response_schemaAdded value: +{
+ "default": false,
+ "description": "Return the complete response_schema. Defaults to false.",
+ "type": "boolean"
+}Input schema / properties / operation_idRemoved value: -{
- "anyOf": [
- {
- "type": "string"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "One operation_id from search"
-}Input schema / properties / operation_idsRemoved value: -{
- "anyOf": [
- {
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- {
- "type": "null"
- }
- ],
- "default": null,
- "description": "Up to 20 operation_ids, for a batch"
-}Input schema / properties / session_idAdded value: +{
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+}Input schema / properties / toolsAdded value: +{
+ "description": "Exact tool names returned by search whose complete contracts are needed. Never invent tool names.",
+ "items": {
+ "minLength": 1,
+ "pattern": "^\\S(?:.*\\S)?$",
+ "type": "string"
+ },
+ "maxItems": 20,
+ "minItems": 1,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / with_quoteRemoved value: -{
- "default": true,
- "description": "Whether each operation is priced for this account before the answer. One round trip per operation; spends nothing.",
- "type": "boolean"
-}Input schema / requiredAdded value: +[
+ "tools"
+]Output schema / propertiesAdded value: +{
+ "error_count": {
+ "type": "integer"
+ },
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "session_id": {
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "minLength": 1,
+ "pattern": "^[A-Za-z0-9_-]{1,128}$",
+ "type": "string"
+ },
+ "success_count": {
+ "type": "integer"
+ },
+ "tools": {
+ "additionalProperties": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "canonical_operation_id": {
+ "type": "string"
+ },
+ "documentation": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "error": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "code": {
+ "type": "string"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ]
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "idempotent": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "read_only": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "boolean"
+ }
+ ]
+ },
+ "response_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "side_effects": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "successful": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "successful"
+ ],
+ "type": "object"
+ },
+ "type": "object"
+ },
+ "total_count": {
+ "type": "integer"
+ }
+}Output schema / requiredAdded value: +[
+ "error_count",
+ "next_steps_guidance",
+ "session_id",
+ "success_count",
+ "tools",
+ "total_count"
+]search17 fields changedInput schema / $schemaAdded value: +"https://json-schema.org/draft/2020-12/schema"Input schema / properties / category / anyOfRemoved value: -[
- {
- "enum": [
- "seo",
- "finance",
- "social",
- "search",
- "sales",
- "mail"
- ],
- "type": "string"
- },
- {
- "type": "null"
- }
-]Input schema / properties / category / defaultRemoved value: -nullInput schema / properties / category / descriptionPrevious value: -"Restrict to one category (seo, finance, social, search, sales, mail). Omit to search everything."New value: +"Restrict retrieval to one category. Omit to search everything. (AIsa-only: tool-router has no equivalent.)"Input schema / properties / category / enumAdded value: +[
+ "seo",
+ "finance",
+ "social",
+ "search",
+ "sales",
+ "mail"
+]Input schema / properties / category / typeAdded value: +"string"Input schema / properties / known_fieldsAdded value: +{
+ "additionalProperties": true,
+ "default": {},
+ "description": "Known values such as ticker, URL, provider, or identifier that improve retrieval.",
+ "type": "object"
+}Input schema / properties / limit / descriptionPrevious value: -"Maximum candidates, 1-10"New value: +"Maximum number of additional direct tool candidates."Input schema / properties / limit / maximumAdded value: +20Input schema / properties / limit / minimumAdded value: +1Input schema / properties / provider_filtersAdded value: +{
+ "default": [],
+ "description": "Optional exact catalog provider keys used to narrow retrieval (for example similarweb). Do not use display brands. Omit this field if the exact key is unknown.",
+ "items": {
+ "type": "string"
+ },
+ "maxItems": 50,
+ "type": "array",
+ "uniqueItems": true
+}Input schema / properties / query / descriptionPrevious value: -"What you need, in plain language, e.g. 'backlinks of a domain', 'recent tweets by a user', 'insider trades for AAPL'. English works best."New value: +"Natural-language capability or task to discover."Input schema / properties / query / maxLengthAdded value: +2000Input schema / properties / query / minLengthAdded value: +1Input schema / properties / session_idAdded value: +{
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "pattern": "^[A-Za-z0-9_-]*$",
+ "type": "string"
+}Output schema / propertiesAdded value: +{
+ "next_steps_guidance": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "canonical_use_case": {
+ "type": "string"
+ },
+ "description": {
+ "type": "string"
+ },
+ "known_pitfalls": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "plan_ref": {
+ "type": "string"
+ },
+ "primary_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "recommended_steps": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "related_tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ }
+ },
+ "required": [
+ "canonical_use_case",
+ "description",
+ "known_pitfalls",
+ "plan_ref",
+ "primary_tools",
+ "recommended_steps",
+ "related_tools"
+ ]
+ },
+ "retrieval_mode": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "string"
+ }
+ ]
+ },
+ "search_id": {
+ "type": "string"
+ },
+ "session_id": {
+ "description": "Reuse the session_id returned by Search in all subsequent tool calls for this task. If omitted, a new session is created.",
+ "maxLength": 128,
+ "minLength": 1,
+ "pattern": "^[A-Za-z0-9_-]{1,128}$",
+ "type": "string"
+ },
+ "tools": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "arguments_schema": {
+ "additionalProperties": true,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ]
+ },
+ "description": {
+ "type": "string"
+ },
+ "execution_supported": {
+ "description": "Whether this router can execute and quote the operation; false retains documentation and discovery only.",
+ "type": "boolean"
+ },
+ "execution_unsupported_reason": {
+ "description": "Why execution and quoting remain unavailable through this router.",
+ "type": "string"
+ },
+ "has_full_schema": {
+ "type": "boolean"
+ },
+ "match_reasons": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "array"
+ }
+ ],
+ "items": {
+ "type": "string"
+ }
+ },
+ "price": {
+ "additionalProperties": true,
+ "type": "object"
+ },
+ "retrieval_debug": {
+ "additionalProperties": false,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "object"
+ }
+ ],
+ "properties": {
+ "fused_rank": {
+ "type": "integer"
+ },
+ "fused_score": {
+ "type": "number"
+ },
+ "lexical_rank": {
+ "type": "integer"
+ },
+ "lexical_score": {
+ "type": "number"
+ },
+ "rerank_admission_rank": {
+ "type": "integer"
+ },
+ "rerank_rank": {
+ "type": "integer"
+ },
+ "rerank_score": {
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "number"
+ }
+ ]
+ },
+ "runtime_availability": {
+ "type": "string"
+ },
+ "vector_view_ranks": {
+ "additionalProperties": {
+ "type": "integer"
+ },
+ "type": "object"
+ },
+ "vector_view_scores": {
+ "additionalProperties": {
+ "type": "number"
+ },
+ "type": "object"
+ }
+ },
+ "required": [
+ "fused_rank",
+ "fused_score",
+ "lexical_rank",
+ "lexical_score",
+ "rerank_admission_rank",
+ "rerank_rank",
+ "runtime_availability",
+ "vector_view_ranks",
+ "vector_view_scores"
+ ]
+ },
+ "summary": {
+ "type": "string"
+ },
+ "tool": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "description",
+ "has_full_schema",
+ "price",
+ "summary",
+ "tool"
+ ],
+ "type": "object"
+ }
+ }
+}Output schema / requiredAdded value: +[
+ "next_steps_guidance",
+ "search_id",
+ "session_id",
+ "tools"
+]use1 field changedInput schema / properties / max_price_usd / descriptionPrevious value: -"Refuse the call before any spend if it would cost more than this many USD"New value: +"Refuse the call before any spend if its quoted price is above this many USD"get_details1 field changedInput schema / properties / include_documentationAdded value: +{
+ "default": false,
+ "description": "Include the complete native public OpenAPI document, reference closure and scoped completeness. Existing execution schemas remain unchanged.",
+ "type": "boolean"
+}batch_useget_detailsget_youtube_searchlist_categoriessearchuseYour agent needs live data — a competitor's traffic, who to contact there, what people are saying, what Google and ChatGPT answer about you, a company's filings. Normally that is six vendor accounts, six sets of keys and six SDKs. This is one URL. **What you can ask for** • "How much traffic does stripe.com get, where does it come from, and who competes for the same keywords?" • "Find 20 Series-B fintech companies in Germany and the heads of marketing there, with emails." • "Does ChatGPT mention our brand when someone asks for the best CRM — and what does it cite?" • "What is X saying about $NVDA today, and what did the stock actually do?" • "Search the web for this, then scrape the three best pages into markdown." **How to use it** Point any MCP client at https://mcp.aisa.one/mcp and sign in with OAuth — there is no key to create or paste. Then just ask: the agent calls search to find the right operation and use to run it. **Why this rather than the source** 26 sources behind one account and one bill — DataForSEO, Semrush, Ahrefs, Similarweb, Apollo, X/Twitter, Instagram, Reddit, Pinterest, YouTube, Tavily, Exa, Perplexity, Firecrawl, CoinGecko, Kalshi, Polymarket, AgentMail and more, 580+ operations. tools/list returns five tools, not 580, so the introduction does not eat your context window. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** One slice at a time: https://mcp.aisa.one/seo/mcp · /finance/mcp · /social/mcp · /search/mcp · /sales/mcp · /mail/mcp · /gtm/mcp, or a single provider like /twitter-api/mcp. Same account, fewer tools listed, and search still reaches everything. Full list at https://mcp.aisa.one/servers
Your agent needs the open web — searched by more than one engine, and read as clean markdown rather than raw HTML. **What you can ask for** • "Search this question with two providers and tell me where they disagree." • "Scrape these 40 URLs into markdown, in one batch." • "Crawl this documentation site and give me every page." • "Do deep research on this topic and cite the sources." • "Find the academic papers behind this claim." **How to use it** Point any MCP client at https://mcp.aisa.one/search/mcp and sign in with OAuth — there is no key to create or paste. 30 tools across several independent providers: Tavily and Exa search, answers, contents and agent runs; Firecrawl scrape, batch scrape, crawl, map and search; Perplexity Sonar, Sonar Pro, reasoning and deep research; Oxylabs AI search and LLM jobs; OpenAI and Anthropic web search; and scholarly search. **Why this rather than the source** Several independent indexes behind one account, because one engine's blind spot is not visible from inside it. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Find the page here, then ask the same agent who links to it or how much traffic it gets — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for the Google results page itself, https://mcp.aisa.one/seo-serp-other-engines/mcp for Bing, Baidu and Naver.
Google is not the whole market. Your agent needs Bing, Yahoo, Baidu, Naver, Seznam and YouTube results — the engines that decide whether you exist in China, Korea, Japan or Central Europe. **What you can ask for** • "What ranks for this term on Baidu, and how different is it from Google?" • "Check Naver results for our Korean brand name." • "Compare Bing and Yahoo results for the same query." • "What comes up on YouTube search for this phrase in Japanese?" • "Take a screenshot of the results page as a user there sees it." **How to use it** Point any MCP client at https://mcp.aisa.one/seo-serp-other-engines/mcp and sign in with OAuth — there is no key to create or paste. 34 tools: organic results from Bing, Yahoo, Baidu, Naver and Seznam in live, regular and raw-HTML forms, YouTube search, an AI summary of a result set, and a rendered screenshot. **Why this rather than the source** The engines that matter outside the US, with the same call shape as the Google ones. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Check the local engine here, then ask the same agent what the site's traffic or backlinks look like in that market — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/seo-serp/mcp for Google itself. https://mcp.aisa.one/seo/mcp for all of it at once — rankings, keywords, backlinks, site health and AI-answer visibility across DataForSEO, Semrush and Ahrefs.
Your agent needs X/Twitter data — who follows a competitor, what a community is posting, who quoted that tweet, what is trending in Japan. Normally that means applying for an X developer account, passing app review, and managing a quota per endpoint. **What you can ask for** • "Who follows @stripe, and which of them are verified?" • "Pull every reply and quote on this tweet and summarise what people object to." • "List this community's moderators and its posts this week." • "What is trending in Japan right now?" • "Give me the full thread context behind this link, including the long-form article." **How to use it** Point any MCP client at https://mcp.aisa.one/twitter-api/mcp and sign in with OAuth — there is no key to create or paste. 29 read tools: users (profile, about, batch lookup by id, search, followers, verified followers, followings, follow check), tweets (timeline, latest, mentions, advanced search, replies, quotes, retweeters, thread context, articles), communities, lists, Spaces and trends. **Why this rather than the source** No developer account to apply for, no app review, no per-endpoint quota to manage. **It is also a door to the rest** The same login reaches 26 sources and 580+ operations. Ask for a handle's followers here, then ask the same agent for that brand's search traffic, its backlinks, or the people to contact — without adding a second server. **What it costs** Finding and inspecting an operation is free. Running one is billed per call at API prices, with no seat and no monthly minimum, and every call takes max_price_usd so an agent cannot overspend by accident. **Where else it reaches** https://mcp.aisa.one/social/mcp for X plus Instagram, Reddit, Pinterest and YouTube; https://mcp.aisa.one/gtm/mcp for those plus Similarweb and Apollo.
Add one secure layer between your agents and this server.
