Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get website goal

analytics_getWebsiteGoal
Read-onlyIdempotent

One saved goal (goalId from getWebsiteGoals).

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>",
      "goalId": "<goalId>"
    },
    "name": "analytics_getWebsiteGoal"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalIdYes
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior2/5

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

Annotations already declare readOnly, idempotent, and closed-world behavior, so the bar is lower, but the description adds essentially nothing beyond them. It does not say what is returned, whether a missing goal errors, or how siteId/objectId scope the lookup.

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?

It is a single short fragment with no wasted words, but it is under-specified rather than concise; the missing verb and object make it read like a field comment rather than a tool description.

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 lookup tool with no output schema and an undocumented goalId, the description should at least say a single goal definition is returned for the given site. It leaves the agent guessing what comes back and how objectId changes the target.

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?

Schema coverage is 67%, with siteId and objectId documented in the schema and goalId carrying only a UUID pattern. The description's only added semantic value is tracing goalId back to getWebsiteGoals; it explains nothing about siteId vs objectId scoping.

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?

"One saved goal" identifies the resource and the singular scope, but there is no verb (get/retrieve) and no statement of what a goal record contains. It does distinguish this from the plural listing sibling only implicitly through the word "One".

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 parenthetical "goalId from getWebsiteGoals" usefully routes the agent to the listing tool to obtain the identifier, which is real when-to-use guidance. There is no guidance on when to prefer the goal-stats siblings instead of the definition record.

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