Skip to main content
Glama

A person's named lists

lists
Destructive

Needs the person's access token. action: list, create, update, delete a named list; add or remove a product or digital plan in it.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "action": "<action>"
    },
    "name": "lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoName
noteNoNote
limitNoMax rows
actionYesOperation to run; help {topic:"lists"} lists each one's arguments
detailNocompact (default) or full
localeNoLanguage, e.g. cs
offsetNoRows to skip
sharedNoShare by link
countryNoCountry code, e.g. CZ
list_idNoList id
digital_idNoDigital plan id
product_slugNoProduct slug

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / action / description
      Added value: +"Operation to run; help {topic:\"lists\"} lists each one's arguments"
    • addedInput schema / properties / detail
      Added value: +{
      +  "description": "compact (default) or full",
      +  "enum": [
      +    "compact",
      +    "full"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Max rows",
      +  "type": "number"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Rows to skip",
      +  "type": "number"
      +}
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already flag this as a non-read-only, destructive, non-idempotent tool, and the description's mention of 'delete' and 'remove' is consistent with them. It adds the auth requirement, which annotations do not cover, but says nothing about what deletion destroys, whether removal is reversible, or how the multi-action dispatch behaves.

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?

Two compact fragments with the auth prerequisite front-loaded before the action catalog; there is no wasted wording, though the sentence structure is telegraphic rather than explanatory.

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 12-parameter, action-multiplexed tool, the description is thin: it lists the action verbs but leaves per-action argument requirements entirely to the schema and the help topic. It is adequate for an agent that reads the schema, but not self-sufficient.

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 12 parameters. The description adds only a mapping of the add/remove actions to product or digital plan entities, plus a pointer to help {topic:'lists'} for per-action arguments, which is marginally useful but not compensating detail.

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

Purpose4/5

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

The description states a concrete resource (a person's named lists) and enumerates the operations: list, create, update, delete, and add/remove a product or digital plan. It is more specific than the bare tool name 'lists', though it does not differentiate from the overlapping sibling 'favorites'.

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?

It gives a prerequisite ('Needs the person's access token') and implies when to use it via the action enumeration, but offers no guidance on when NOT to use it or on choosing between it and siblings such as favorites or product.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources