Skip to main content
Glama

apis-io

by io.apis
OverviewDiscussionsAdmin

list_lists

Read-only

UNDERSTANDING — List the lists/shortlists you own. Priced B1 (single-entity synthesis) — $0.01 per call under pay-as-you-go; included in Understanding and Influence. See apis://prices.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contextNoOptional: 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.

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+}
  2. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description is consistent with that. It adds pricing and plan-inclusion details ('$0.01 per call', 'included in Understanding and Influence'), which are not present in annotations and help the agent weigh cost. It does not cover rate limits or data freshness, but the added cost transparency is meaningful.

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

Conciseness5/5

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

The core action is stated in one short sentence, followed by compact pricing data and a reference link. No wasted words; the purpose is front-loaded and the additional pricing context is relevant and concise.

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

Completeness4/5

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

For a simple, no-required-parameter read tool, the description gives enough context to invoke it correctly. It does not specify the return format (e.g., fields, pagination), and no output schema exists, so an agent may not know what each list object contains. However, the low complexity and self-explanatory name make this a minor gap.

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?

The only parameter, context, is fully documented in the input schema (100% coverage), so the description need not repeat it. The tool description adds no extra meaning beyond the schema, matching the baseline for high schema coverage.

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?

Description uses a specific verb and resource ('List the lists/shortlists you own'), clearly scopes to self-owned lists, and is easily distinguished from siblings such as get_list, create_list, and list_saved_searches. The 'UNDERSTANDING' prefix adds category context without obscuring the action.

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

Usage Guidelines3/5

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

The phrase 'you own' implies the primary use case (retrieving your own lists), but the description does not explicitly name alternatives or state when not to use this tool. No exclusion criteria or sibling routing is provided, leaving the agent to infer boundaries based on the name alone.

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
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources