Skip to main content
Glama

Sextant Web - Website GEO, SEO, and Analytics

Get website goals

analytics_getWebsiteGoals
Read-onlyIdempotent

The site's saved goals, each a page visit or a custom event.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
searchNoSearch text used to filter results.
siteIdYesThe Sextant site ID.
objectIdNoOptional: a short link or tracking pixel of this site, to read its analytics instead of the site's.
pageSizeNoNumber of results per page.
maxResultsNoMaximum number of results to include.

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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered elsewhere. The description adds only a domain gloss on what a goal is; it says nothing about pagination behavior, result ordering, empty-site behavior, or permissions — all of which would be genuinely additive for a 6-parameter paginated 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?

A single compact sentence with the resource front-loaded and zero filler. It is arguably too terse rather than padded, but there is no redundant or wasted wording to trim.

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?

With no output schema, the description carries some burden to say what the goal objects contain (metric, target, event name, etc.), and it only offers a one-line definition. For a simple read-only list tool with fully documented parameters this is minimally adequate, but it leaves the return shape and filtering semantics unexplained.

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 description coverage is 100%, so every parameter (page, pageSize, maxResults, search, siteId, objectId) is already documented in the schema. The description adds no meaning about filtering, the objectId override, or how maxResults interacts with pageSize, so the baseline 3 applies.

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 description names the resource ('the site's saved goals') and clarifies what a goal is ('a page visit or a custom event'), which is more than a restatement of the name. However, it is a noun phrase with no verb (list/retrieve) and never distinguishes this plural listing tool from the sibling analytics_getWebsiteGoal, which presumably fetches a single goal. Purpose is inferable but not sharp.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of when to prefer analytics_getWebsiteGoal or analytics_getWebsiteGoalStats, and no stated prerequisites beyond the required siteId in the schema. The agent must infer the listing-vs-single-goal split from tool names alone.

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