Skip to main content
Glama

Refresh Site Profile

qualitykit.refresh_site_profile

Refresh a website's SEO/AEO profile from repository evidence, updating only stale fields when a configured Cloud model is available and returning an agent-ready brief offline.

Instructions

Prefer Cloud model refresh when Pro + MODEL_* are configured (stale fields only; material stays pending). Offline: returns a host-agent brief from repo evidence.

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": {
      "projectRoot": "<projectRoot>"
    },
    "name": "qualitykit.refresh_site_profile"
  }
}

Input Schema

NameRequiredDescriptionDefault
apiKeyNo
siteUrlNo
apiBaseUrlNo
projectRootYesAbsolute path to the website repository root

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

C2.9/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that only stale fields are refreshed, material stays pending, and offline mode returns a host-agent brief from repo evidence, but it omits whether the operation writes data, what permissions are needed, and what the response contains.

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 description is two compact sentences with no filler, and the cloud-versus-offline distinction is front-loaded. The density is appropriate, though the jargon makes it less immediately clear than a plain-language statement would be.

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?

For a four-parameter tool with no annotations and no output schema, the description is too thin. It does not explain the profile fields affected, what "material" means, what the host-agent brief contains, or how the three undocumented parameters should be supplied.

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 description coverage is only 25%, with just projectRoot documented, so the description should compensate for apiKey, siteUrl, and apiBaseUrl. It mentions Pro + MODEL_* configuration but does not map that to the apiKey parameter or explain the other undocumented parameters, leaving their semantics unclear.

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

Purpose3/5

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

The name and title identify a refresh operation on a site profile, but the description leads with jargon like "Cloud model refresh" and "host-agent brief" rather than plainly stating what is refreshed. It distinguishes cloud versus offline behavior, yet an agent must infer the core action from the tool name.

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 gives a conditional preference: use Cloud model refresh when Pro + MODEL_* are configured, otherwise offline returns a brief. It does not explain when to choose this tool over siblings such as get_site_profile or update_site_profile, nor does it state prerequisites or exclusions beyond the configuration condition.

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