list_gridsRetrieve your account's grids, newest first, optionally filtered by listing or keyword. Get grid IDs to use with get_grid, get_history, or schedule_grid. Free.
The account's grids, newest first, optionally for one listing (place_id) or one exact keyword. Returns grid_id values to use with get_grid, get_history or schedule_grid. Free.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| before | No | ||
| keyword | No | ||
| place_id | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, so the safety profile is covered; the description adds non-annotation context: newest-first ordering and a 'Free' cost signal. Pagination mechanics (limit/before) remain undescribed.
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?
Two dense sentences with the resource and ordering front-loaded, then filters, then the return/follow-up routing and cost. No wasted 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?
With no output schema and only readOnlyHint, the description usefully covers scope, ordering, return type (grid_id), follow-up tools, and cost. The main gap is lack of guidance on limit/before pagination for a list endpoint.
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?
Schema coverage is 0%, so the description must compensate. It clarifies place_id ('one listing') and keyword ('one exact keyword'), but says nothing about limit or before, leaving two of four parameters undocumented.
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 a specific verb+resource ('The account's grids') plus scoping ('newest first', 'optionally for one listing') and distinguishes itself from siblings by naming the follow-up tools (get_grid, get_history, schedule_grid). Clear, though it doesn't explicitly contrast with get_grid/run_grids.
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?
Explains when to use it (retrieve grids, optionally filtered by place_id or keyword) and routes to the correct follow-up tools once grid_id is obtained. No explicit when-not, but the filtering conditions give solid context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.