Skip to main content
Glama

List takes

list_takes
Read-only

Takes of an item, i.e. the generations recorded against it: each with id, status, is_starred and outputs (assets with url). item is its id, slug or @slug. New takes are not starred automatically; review the outputs and call star_take on the one to keep.

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": {
      "project": "<project>",
      "item": "<item>"
    },
    "name": "list_takes"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemYes
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 and openWorldHint=true, so the safety profile is covered structurally; the description's real contribution is the non-obvious fact that new takes are not starred automatically, which prevents an agent from assuming a default selection. It stops there — no mention of result volume, ordering (newest first?), or whether output URLs expire, which matter for a list of generations.

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 sentences, front-loaded with the resource definition and back-loaded with the workflow instruction. The inline backticked field list is slightly redundant given an output schema exists, but it is short enough to earn its place as a quick orientation.

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?

Adequate for a two-parameter read-only lister with an output schema, which removes the burden of documenting return values. Gaps remain around the `project` parameter, ordering/pagination of results, and an explicit pointer back to get_item when only one take is needed.

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?

With 0% schema description coverage the description must carry the parameters, and it only half does: it usefully explains that `item` accepts an id, slug, or `@slug`, but leaves `project` entirely unexplained relative to `item`. One of two required parameters is well-covered, the other is not.

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 with a definitional gloss: 'Takes of an item, i.e. the generations recorded against it,' which tells an agent what a take is without opening a schema. It also names the fields returned (id, status, is_starred, outputs with url), separating it from generic item/asset listers by implication, though it never explicitly contrasts with list_items or list_assets.

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?

Provides actionable follow-up guidance: 'review the outputs and call star_take on the one to keep,' naming a concrete sibling and the condition that selects it. What is missing is a when-not-to-use signal (e.g. use get_item for a single item's metadata), so the routing is one-directional.

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