Skip to main content
Glama
Sign In

apis-io

by io.apis
OverviewDiscussionsAdmin

add_to_list

Idempotent

UNDERSTANDING — Add providers/APIs (by slug or aid) to one of your lists. Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

NameRequiredDescriptionDefault
idYesList id, as create_list returns it or list_lists lists it.
contextNoOptional: one sentence on why you are asking. Never used to rank; read only if a result is wrong.
membersYesProvider slugs and/or API aids to add, e.g. ["stripe","adyen:checkout-api"].

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / context / description
      Previous value: -"Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable."New value: +"Optional: one sentence on why you are asking. Never used to rank; read only if a result is wrong."
  2. Changed2 schema fields changed
    • addedInput schema / properties / id / description
      Added value: +"List id, as create_list returns it or list_lists lists it."
    • addedInput schema / properties / members / description
      Added value: +"Provider slugs and/or API aids to add, e.g. [\"stripe\",\"adyen:checkout-api\"]."
  3. Changed1 schema field changed
    • addedInput schema / properties / context
      Added value: +{
+  "description": "Optional: why you are asking. One sentence — the task you are trying to complete, or what you expect to get back. Never included in the answer and never used to rank; it is read only when a result turns out to be wrong, which is when knowing the intent is what makes the report actionable.",
+  "type": "string"
+}
  4. Added

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already disclose the safety profile (idempotentHint=true, destructiveHint=false), so the description's main addition is cost context (B1, $0.01/call) and the note that 'context' is never used to rank. It does not state what happens on duplicate members beyond what idempotentHint implies, so the added value is moderate.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The core action is front-loaded in a single clause, with pricing appended as a secondary pointer to apis://prices. Efficient overall, though the 'UNDERSTANDING —' prefix is slightly noisy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple three-parameter mutation with no output schema, the description covers the core action and cost, but omits operational details that would help an agent (e.g., behavior on duplicates, whether the list must be owned, partial-failure handling). Adequate but with clear gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all three parameters, including the 'aid' format example. The description only echoes the 'by slug or aid' phrasing, which the member schema already covers. Baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (add), resource (providers/APIs), target (one of your lists), and the accepted identifier forms (slug or aid). It is readily distinguishable from siblings like create_list, delete_list, and get_list.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use guidance is given: it doesn't say when to add vs. create a new list, nor does it mention prerequisites such as obtaining the list id first (only the schema hints at this). The only context is the pricing tier, which is not usage guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All apis-io toolsInspect
Try in Browser
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources