agentseo_content_title_metaGenerate SEO title and meta description options for a URL or markdown page.
| Name | Required | Description | Default |
|---|---|---|---|
| url | No | Page URL to scrape | |
| sync | No | ||
| target | No | Optional target brand, domain, or product | |
| keyword | Yes | ||
| page_type | No | auto | |
| current_title | No | ||
| page_markdown | No | Page markdown when no URL exists | |
| current_meta_description | No |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description must disclose behavior but only says it 'generates options' without detailing output format, count, or how inputs are prioritized (url vs markdown).
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 front-loaded sentence, which is concise. However, it could benefit from a bit more detail without becoming verbose.
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 8 parameters, no output schema, and no annotations, the description is insufficient for an agent to fully understand tool behavior and expected outcomes.
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?
Schema coverage is only 38%, and the description adds no additional parameter clarity beyond the schema's own descriptions. It does not explain the role of most parameters.
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 it generates SEO title and meta description options from a URL or markdown page. It is specific and distinguishes from other content tools by naming the exact output type.
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?
No guidance on when to use this tool vs alternatives. No mention of prerequisites or scenarios where this is not appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.