get_filmsFetch enriched public films from a Letterboxd user's watch history, with pagination and cache refresh options.
Return enriched public films watched by a Letterboxd user.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| offset | No | ||
| refresh | No | ||
| username | Yes |
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | ||
| limit | Yes | ||
| total | Yes | ||
| offset | Yes | ||
| has_more | Yes | ||
| username | Yes | ||
| fetched_at | Yes |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover read-only/idempotent; description does not add additional behavioral details like caching or rate limits.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
One sentence, no unnecessary words.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
While output schema exists, the description omits parameter roles (pagination, refresh) and the meaning of 'enriched'; for a tool with four parameters, this is insufficient.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
None of the four parameters (username, limit, offset, refresh) are described in the schema or description; description only references user implicitly.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States it returns enriched public films for a Letterboxd user, using a specific verb and resource, and distinguishes from siblings like get_profile and get_diary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance on when to use this over get_profile or get_diary; no conditions or alternatives mentioned.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.