Skip to main content
Glama

Get my lists

get_account_lists
Read-only

Fetch your TMDB account's custom lists with IDs and item counts, paging through results to browse saved movie and TV collections.

Instructions

The custom lists I created on TMDB, with their IDs and item counts.

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": "get_account_lists"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoResults page, 1-500. Each page holds up to 20 results.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuine value by disclosing the shape of the payload (IDs plus item counts), which tells the agent this is a summary listing rather than full list contents — but it says nothing about ordering, pagination, or empty-account behavior.

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?

One tight sentence with zero filler that front-loads the resource and immediately states what the response contains. Nothing is redundant or padded.

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 trivial read-only single-parameter tool with no output schema, disclosing that IDs and item counts are returned is close to sufficient. The remaining gap is that account/auth context and the summary-vs-full-contents distinction are left implicit.

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%: the single optional page parameter is fully documented in the schema (range 1-500, 20 results per page). The description adds no further meaning about paging, so the baseline of 3 applies.

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?

States a specific resource — the custom lists the authenticated user created on TMDB — and what each carries (IDs and item counts). It is clear, but it never distinguishes itself from the singular get_list or get_account_items siblings, so scope boundaries must be inferred.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g. requiring an authenticated account session), and no pointer to alternatives such as get_list for a single list's contents. The agent must guess from the name alone.

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