Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

update_milestone

Partially update a milestone by ID or slug—change name, description, dates, color, or move it while keeping startDate on or before endDate.

Instructions

Partially update a milestone by id or slug — any combination of name, description, startDate, endDate and color. A milestone can be moved but never unscheduled, and startDate must stay on or before endDate.

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

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 real behavioral constraints: partial-update semantics, the prohibition on unscheduling, and the date ordering invariant. It omits what happens on invalid input, required permissions, and whether unspecified fields are left untouched (only implied by 'partially update').

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, both dense: the first front-loads the operation, identifier, and field list; the second carries the two invariants. Nothing is redundant or padded.

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 mutation tool with no annotations and no output schema, the description covers what can change, how the target is identified, and the key invariants. It stops short of return-value or error behavior, which an agent may still need when handling failures.

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 at all, so the description is the only source of parameter meaning, and it supplies the identifier keys (id or slug) and the five mutable fields. It does not specify formats such as date encoding or accepted color values, which leaves a gap for a zero-property schema.

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 description states a specific verb and resource ('Partially update a milestone') and names the lookup keys (id or slug) plus the exact updatable fields. An agent can distinguish this from create_milestone or assign_task_to_milestone without opening any 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?

It makes clear this is a partial update ('any combination of' fields) and states two hard rules: a milestone can be moved but never unscheduled, and startDate must stay on or before endDate. It gives no explicit when-not guidance or named alternative for full replacement, so it falls just 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