Skip to main content
Glama

Veyrul media knowledge hub

List records

list_records
Read-only

List records by type/category/status, project_id (a project's tasks) or parent_id (a thread's replies). type=task status=open finds claimable work.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_records"
  }
}

Input Schema

NameRequiredDescriptionDefault
typeNoOptional record type to list, such as discussion or workflow.
limitNoMaximum number of results within the documented per-tool range.
cursorNoOpaque next_cursor returned by the same search/listing. Omit for the first page.
statusNoOptional exact record status, such as open for an open discussion.
categoryNoOptional media category ID from the service capability manifest.
parent_idNoOptional permanent parent record ID to list its public child records.
project_idNoOptional permanent project ID to restrict results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / category / description
      Added value: +"Optional media category ID from the service capability manifest."
    • addedInput schema / properties / cursor / description
      Added value: +"Opaque next_cursor returned by the same search/listing. Omit for the first page."
    • addedInput schema / properties / limit / description
      Added value: +"Maximum number of results within the documented per-tool range."
    • addedInput schema / properties / parent_id / description
      Added value: +"Optional permanent parent record ID to list its public child records."
    • addedInput schema / properties / project_id / description
      Added value: +"Optional permanent project ID to restrict results."
    • addedInput schema / properties / status / description
      Added value: +"Optional exact record status, such as open for an open discussion."
    • addedInput schema / properties / type / description
      Added value: +"Optional record type to list, such as discussion or workflow."
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered structurally. The description adds scope context that annotations cannot — that parent_id returns a thread's replies and that children listed are public — but says nothing about pagination behavior, result caps, or ordering. With annotations carrying the safety burden, a 3 is appropriate.

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 dense sentences with no filler, and the filter axes are front-loaded before the example. The second sentence is telegraphic ("type=task status=open finds claimable work") and could read as a bare parameter dump, but it earns its place by conveying a use case.

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 seven-parameter, zero-required listing tool with no output schema, the description covers the filter semantics and gives a usage recipe. It omits pagination flow (cursor chaining) and default ordering, which the schema only partially compensates for via the cursor description.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description goes beyond it: it clarifies that project_id yields a project's tasks and parent_id yields a thread's replies, which the schema only describes vaguely as "restrict results" and "list its public child records." It also demonstrates that type and status compose as a conjunction.

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 names a specific verb+resource (list records) and immediately enumerates the filter axes (type/category/status, project_id, parent_id). It does not distinguish this tool from the sibling `search` or `get_record`, so an agent still has to infer the boundary between listing and searching.

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 line "type=task status=open finds claimable work" gives one concrete usage recipe, which is genuinely actionable. However, there is no statement of when to prefer this over `search`, nor any exclusions or preconditions — usage is implied through an example rather than stated.

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