Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get project context

seo_get_project_context
Read-onlyIdempotent

Reads the site's business profile: business overview, positioning, ideal customer profiles (icps: up to 10, each with name and description), competitors, key pages with their role, and the recent research log. Free. The research log lists research already bought. missingSections lists the sections that are still empty; seo.update_project_context fills them.

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": "seo_get_project_context"
  }
}

Input Schema

NameRequiredDescriptionDefault
siteIdYesThe Sextant site ID.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered; the description goes beyond that by disclosing cost (free), the 10-ICP cap, and the semantic meaning of missingSections and the research log. The only remaining gap is return format/pagination, which is minor for a profile read.

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?

Densely packed and front-loaded: capability first, expanded field meanings, then the follow-up action. The parenthetical 'icps: up to 10, each with name and description' earns its place, but the fragment 'missingSections lists the sections that are still empty' lacks a lead-in and reads as an incomplete sentence.

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

Completeness5/5

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

With no output schema, the description carries the return-shape burden itself and does so by enumerating each returned section, including field-level notes like the 10-ICP ceiling. For a one-parameter read tool whose annotations already cover safety, no information an agent would need to call it correctly is missing.

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 parameter with a schema description ('The Sextant site ID.') covering it, so baseline 3 applies. The description adds nothing about siteId resolution or scoping, nor does it explain what happens if the site has no profile yet.

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 description names a specific verb (reads) and resource (the site's business profile) and then enumerates the returned sections: business overview, positioning, ICPs, competitors, key pages, research log, and missingSections. An agent can distinguish this from the ai_visibility/audit/rank-tracker siblings purely from the text, since those resources are not mentioned here.

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?

Usage is signaled inside the description: 'Free' tells the agent this call is cheap, 'The research log lists research already bought' warns against re-purchasing work, and 'missingSections ... seo.update_project_context fills them' establishes the read-then-fill workflow with a concrete alternative. It stops short of explicit when-not-to-call guidance, so it falls just under a 5.

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.

Resources