Skip to main content
Glama

Get a list

get_list
Read-only

Use this when you need one list's details: its kind, its folder, how many rows it holds, whether rows are still being added, how many of its people have an email address or a phone number, and its own columns. It does not return the rows themselves. Free.

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": {
      "listId": "<listId>"
    },
    "name": "get_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
listIdYesThe list's id.

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the safety profile is free. The description adds context the annotations cannot carry: the shape of what comes back (counts, flags, column metadata, no rows) and a cost signal ('Free'), which is genuinely useful for planning. It omits behavior on a missing or invalid listId, which is the main remaining gap.

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?

One compact sentence, front-loaded with the trigger condition, followed by a useful exclusion and a cost note. The long enumeration of returned fields is dense but every item earns its place since there is no output schema to describe returns.

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 single-parameter read tool with no output schema, the description does the heavy lifting of describing the return payload field by field, which is exactly what an agent needs to decide whether to call it. Only the failure/not-found behavior is unaddressed.

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% and the single listId parameter is fully constrained by pattern and length, so the schema carries the semantics. The description adds nothing about the id format or where an id comes from (e.g., list_* tools), which is the baseline expectation at this coverage level.

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?

The description names a specific verb and resource ('one list's details') and then enumerates exactly what that detail surface covers: kind, folder, row count, enrichment state, channel coverage, and columns. It also explicitly carves out the excluded sibling behavior ('It does not return the rows themselves'), so an agent can distinguish it from get_list_rows without opening either schema.

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

Usage Guidelines4/5

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

'Use this when you need one list's details' gives a clear positive trigger, and the row-exclusion sentence tells the agent when this is the wrong tool for row-level data. It never names the better alternative explicitly (get_list_rows), so the routing is inferable 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