seocrawl-mcp

Official

by SEOcrawl

Overview Schema Source Related Servers Discussions Admin

JavaScript

Remote

create_task

Create a task for SEO workflow management, specifying title, optional details, assignee, priority, and taskbox.

Instructions

Create a task (title required + optional description, assignee, priority, taskbox).

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_task"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 25, 2026

TDQS

C2.9/5.0

Behavior2/5

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

The description only says 'Create a task' without disclosing side effects, authentication needs, or behavior on invalid fields. Since no annotations exist, the description provides insufficient transparency.

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?

One sentence with no fluff. Every word adds value, listing required and optional fields concisely.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, no output schema, and an empty input schema, the description is insufficient. It lacks detail on data formats, error handling, or return values, making it hard for an agent to use 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?

Though the input schema is empty, the description lists specific fields (title, description, assignee, priority, taskbox) with semantics, adding significant value beyond the schema. The schema coverage is misleadingly 100% but empty, so description carries the burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states 'Create a task' and lists fields, which is clear. However, it contradicts the input schema by claiming 'title required' and other optional fields, while the schema has no defined properties. This ambiguity reduces clarity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No usage context or alternatives are provided. The agent is not informed when to use this tool versus update_task or add_comment, nor any prerequisites.

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