Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

list_milestones

Lists every roadmap milestone on a property board with IDs, dates, progress, state, and task counts, providing the slug or ID needed to update a milestone or assign tasks.

Instructions

Every roadmap milestone on a property's board: id, slug, name, description, start_date and end_date (Y-m-d), color, progress (0–100, computed from the tasks sitting in the DONE column), state (upcoming / active / overdue / done / at_risk) and the task and done counts. Pass a returned id or slug to update_milestone or assign_task_to_milestone.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose useful behavior: progress is computed from tasks in the DONE column, state values are enumerated (upcoming / active / overdue / done / at_risk), and dates are formatted Y-m-d. It does not cover pagination, ordering, or whether the list is scoped by any permission/property argument, 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with scope and then the chaining instruction. The field enumeration is long but earns its place because there is no output schema to document the return shape.

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?

With no output schema and no annotations, the definition compensates well by describing the returned fields and computed values. It falls slightly short on operational details such as pagination or result limits, but is otherwise sufficient to call the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so the baseline is 4; the description instead spends its space defining the output fields (id, slug, progress, state, task/done counts), which is the relevant semantics here.

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 definition opens with a specific verb and resource ('Every roadmap milestone on a property's board') and then enumerates exactly what is returned, so an agent can distinguish it from list_tasks or list_taskboxes at a glance.

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?

The final sentence makes the downstream workflow explicit: pass a returned id or slug to update_milestone or assign_task_to_milestone. That tells the agent when this tool is the right predecessor, but there is no statement of when not to use it or how it relates to the other list_* tools.

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

Deploy Server

Other Tools