create_tag
Create keyword, URL, or combined tags with optional hex colors to categorize and organize SEO data.
Instructions
Create a keyword/url/both tag (optional hex color).
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Create keyword, URL, or combined tags with optional hex colors to categorize and organize SEO data.
Create a keyword/url/both tag (optional hex color).
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description does not disclose behavioral traits such as duplicate behavior, side effects, or authentication requirements for this write operation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence with no unnecessary words or redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the lack of annotations and output schema, the description is too brief, omitting essential details about input fields and expected behavior, making it incomplete for effective use.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
With zero defined parameters in the schema, the description adds meaning by mentioning 'keyword/url/both' and 'optional hex color', but fails to specify exact parameter names or types.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb 'create' and the resource 'tag' with specific types ('keyword/url/both'), distinguishing it from siblings like 'delete_tag' and 'create_tag_rule'.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The context 'create a keyword/url/both tag' implies when to use this tool, but there is no explicit guidance on when not to use it or comparison to alternatives.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/SEOcrawl/seocrawl-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server