Skip to main content
Glama

SEO Rank Fixer

Site profile

site_profile
Read-onlyIdempotent

The site owner's own description of the business behind one site: what it sells, who it is for, its brand voice, key offers, things to avoid and preferred spelling. Use it to keep anything you write for the site on-brand.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "siteId": "<siteId>"
    },
    "name": "site_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesA site id from list_sites.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so safety and repeatability need no restating. The description adds useful context beyond that: the profile is owner-authored (a first-party, authoritative source) and spans voice, offers, exclusions and spelling preferences. It says nothing about behavior when a site has no profile, how large the response is, or whether the content is cached, which keeps it at an adequate rather than rich level.

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?

Two sentences, both earning their place: the first front-loads what the profile contains, the second states the purpose. The colon-separated field list packs a lot of meaning into one clause without filler. Nothing is repeated from the title or annotations.

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

Completeness4/5

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

This is a simple single-parameter read tool with complete annotations and a fully documented schema, so little burden falls on the description. Because there is no output schema, the field enumeration in the description usefully previews what comes back. Only the no-profile / error case is unaddressed, which is a minor gap at this complexity.

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

Parameters3/5

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

There is a single required parameter, siteId, and schema coverage is 100%, with the schema already explaining it comes from list_sites. The description contributes no additional parameter meaning, such as what happens with an unknown or inaccessible site id. With the schema fully documented, the baseline of 3 applies.

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 names a specific resource ('the site owner's own description of the business behind one site') and enumerates its contents: what it sells, audience, brand voice, offers, things to avoid, spelling. The retrieval verb is only implied by 'Use it to keep anything you write... on-brand', so the action is clear but not stated outright. It is distinguishable from siblings like site_audit or site_performance, which suggest measurement rather than brand context.

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

Usage Guidelines4/5

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

The final clause gives a concrete trigger: use it before writing anything for the site, to stay on-brand. That is clear situational guidance rather than a generic 'use as needed'. It stops short of exclusions or naming a sibling to prefer in other circumstances, so it does not reach the explicit when/when-not bar.

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.