serpmantics

create_score

create_score

Analyze content optimization score

Analyzes the optimization score of the provided content for a specific guide

MCP channel defaults: this tool sends scoreProgressive=false, includeEmbedding=false when you leave them out. That is specific to this channel and overrides the default documented on those parameters, which describes the REST API. What it changes in the response: with scoreProgressive=false, contentAnalysis.progressiveScores comes back empty ({}); with includeEmbedding=false, contentAnalysis.embeddingAnalysis is omitted from the response. Set a flag to true in your arguments to get its content back; any value you do pass is sent unchanged, including false. The whole response is handed to the model, and this is where most of its size goes, so it is opt-in on this channel: ask only for what you are going to read.

Input Schema

TableJSON Schema

Name	Required	Description
`content`	Yes	Content to analyze
`guideId`	Yes	ID of the guide to analyze
`pageUrl`	No	Optional. Read only for a visitor of a guide shared in read-only mode: the URL of one of the guide's SERP pages, whose stored content is then analysed instead of the guide's text. Ignored for the owner and for a guide shared in edit mode. Unknown URL: the guide's text is analysed.
`saveToGuide`	No	Whether to save the content and the analysis score back to the guide (default: true)
`includeEmbedding`	No	Whether to compute the semantic embedding analysis, i.e. proximity and PCA (default: true). When false, the embeddingAnalysis key is omitted from the response. Null is treated as "not provided", so the default applies.
`scoreProgressive`	No	Whether to compute the progressive score build-up curve (default: true). When false, progressiveScores is returned empty. Null is treated as "not provided", so the default applies.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 24, 2026

addedInput schema / properties / pageUrl

Added value: +{
+  "description": "Optional. Read only for a visitor of a guide shared in read-only mode: the URL of one of the guide's SERP pages, whose stored content is then analysed instead of the guide's text. Ignored for the owner and for a guide shared in edit mode. Unknown URL: the guide's text is analysed.\n",
+  "type": "string"
+}

Changed2 schema fields changedSep 19, 2026

addedInput schema / properties / includeEmbedding

Added value: +{
+  "description": "Whether to compute the semantic embedding analysis, i.e. proximity and PCA (default: true). When false, the embeddingAnalysis key is omitted from the response. Null is treated as \"not provided\", so the default applies.\n",
+  "type": "boolean"
+}

addedInput schema / properties / scoreProgressive

Added value: +{
+  "description": "Whether to compute the progressive score build-up curve (default: true). When false, progressiveScores is returned empty. Null is treated as \"not provided\", so the default applies.\n",
+  "type": "boolean"
+}

First observedJul 16, 2026

TDQS

A4/5.0

Behavior4/5

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

With no annotations, the description carries the burden and it does substantial work: it reveals channel-specific defaults (scoreProgressive=false, includeEmbedding=false), their exact effect on the response, and that the response is passed to the model in full, making flags opt-in. It does not discuss the saveToGuide side effect, but that is already documented in the schema.

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

Conciseness4/5

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

The definition is front-loaded with the purpose, and the long second paragraph is dense with necessary channel-specific behavior rather than filler. It could be slightly tighter, but every sentence earns its place for an agent selecting this tool.

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?

The description is complete for the non-obvious flag behavior, but with no output schema it does not explain the overall return shape of the optimization score or how saveToGuide behaves in the analysis flow. An agent can invoke the tool correctly, but might not know the full response structure.

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?

Schema coverage is 100%, so the schema supplies the basic parameter meanings. The description adds value beyond that by explaining that the documented defaults for scoreProgressive and includeEmbedding describe the REST API and are overridden in this MCP channel, and by clarifying the response-size tradeoff.

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

Purpose5/5

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

The first sentence names a specific action and resource: 'Analyze content optimization score' on 'provided content for a specific guide'. This makes it distinguishable from sibling create_* tools such as create_eeat or create_guides, and avoids the tautology of just echoing the title.

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

Usage Guidelines3/5

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

The description implies the use case by saying it analyzes the optimization score for a guide, but it never explicitly contrasts this with sibling tools or states when not to use it. No alternative tools are named, so an agent must infer selection from the resource name.

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

All serpmantics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?