Skip to main content
Glama
seocrawl-mcp

seocrawl-mcp

Official

assign_task_to_milestone

Link an SEO task to a milestone using a UUID, slug, or task URL, or unlink it by omitting the milestone. Each task belongs to at most one milestone.

Instructions

Link a task to a milestone, or unlink it by leaving the milestone out. The ticket takes a UUID, a slug or a full browser task URL, and a task belongs to at most one 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": "assign_task_to_milestone"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It does disclose a genuinely important behavioral constraint: a task belongs to at most one milestone, implying that relinking replaces the previous association and unlinking removes it. It says nothing about required permissions, whether an unlink of an unlinked task errors, or what the call returns.

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 tight sentences, front-loaded with the primary action and immediately followed by the inverse mode and the identifier formats. No filler or redundant restatement of the tool name.

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?

With zero annotations, no output schema, and an empty parameter schema, the description does a fair job covering the essentials (modes, identifier formats, cardinality constraint). It leaves gaps on error behavior when unlinking a task with no milestone, permissions, and the shape of the response, which matter for a mutation tool with no structured support.

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 defines no properties at all (additionalProperties: true), so the description is the only source of parameter meaning, and it delivers: the task identifier accepts a UUID, a slug, or a full browser task URL, and the milestone argument is optional and drives the link/unlink mode. It does not name the actual argument keys, which leaves some guesswork about how to pass them.

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?

The description gives a specific verb-plus-resource: link a task to a milestone, plus the inverse operation (unlink by omitting the milestone). Sibling tools like create_milestone, update_milestone and update_task are clearly different resources/operations, so the agent can differentiate on behavior even though no sibling is named explicitly.

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 states the condition that selects the unlinking mode (leave the milestone out), which is the main ambiguity for this tool. It does not say when to prefer this over update_task for the same assignment, nor any prerequisite checks, so it falls short of naming alternatives explicitly.

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