Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

create_milestone

Create a dated roadmap milestone with a required name and start/end dates, plus optional description and color; attach tasks afterward to organize work.

Instructions

Create a dated roadmap milestone. name plus startDate and endDate (Y-m-d, start on or before end) are required; description and a #RRGGBB color are optional. Tasks are attached afterwards with 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": "create_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully reveals validation behavior (startDate on or before endDate) and which fields are optional, but says nothing about permissions required, what is returned (e.g., a milestone identifier), or when the milestone becomes visible.

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 the action and immediately followed by the required/optional field breakdown. Every clause carries information: formats, the date-ordering rule, color syntax, and the follow-up tool.

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 creation tool with no annotations and no output schema, the description covers everything needed to invoke it correctly, including field formats and the adjacent assignment step. It could be stronger by noting the return value or any permission requirement, but nothing essential to the call is missing.

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?

The input schema declares no properties, so the description is the only source of parameter meaning, and it delivers: name, startDate, endDate marked required with a Y-m-d format and an ordering constraint, plus description and a #RRGGBB color as optional. It loses a point only because the schema admits arbitrary additional properties and the description gives no hint about other acceptable fields.

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?

States a specific verb and resource plus scope: 'Create a dated roadmap milestone.' It also names the adjacent operation's tool (assign_task_to_milestone) for attaching tasks, so an agent can tell creation from attachment and from update_milestone without opening a schema.

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?

Gives clear usage context and a follow-up workflow: tasks are attached afterwards via assign_task_to_milestone, which tells the agent this tool does not handle task assignment. It stops short of explicit when-not-to-use guidance (e.g., updating an existing milestone instead), so it falls short of a 5.

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