Skip to main content
Glama

AgentSEO Content Refresh Brief

agentseo_content_refresh_brief

Create a refresh brief for an existing URL and keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesExisting page URL
syncNo
keywordYesTarget keyword
languageNoen
locationNoUnited States
scrape_depthNoh3

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must disclose behavioral traits. It only says 'Create a refresh brief' without explaining side effects, required permissions, or what the brief entails. Vague for a creation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very concise single sentence, but it lacks important details. While no waste, it is under-specified rather than efficiently informative.

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?

With no output schema and 6 parameters, the description is insufficient. It does not clarify what a refresh brief is, expected outputs, or how parameters affect behavior. Incomplete for effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 33% (only url and keyword have descriptions). The description does not add meaning beyond listing url and keyword, failing to explain sync, language, location, or scrape_depth. Does not compensate for low coverage.

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 clearly states the verb 'Create' and the resource 'refresh brief' for an existing URL and keyword. It differentiates from siblings like agentseo_content_brief by specifying 'refresh', but doesn't explicitly distinguish from other tools.

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 guidance on when to use this tool versus alternatives like agentseo_content_brief. No prerequisites or exclusions mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.