Skip to main content
Glama

Tally by Outpost

Goals

get_goals
Read-onlyIdempotent

Every goal completed in the period with completions, converting visitors, conversion rate and the revenue of converting visitors; give goal for one goal's properties. Lists the site's funnels.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_goals"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoA custom range's last day (YYYY-MM-DD), with from.
fromNoA custom range's first day (YYYY-MM-DD), with to. Up to 366 days, not past today.
goalNoA goal's name, for its properties' breakdown.
siteNoThe site's id. Optional: the API key's site is the one read.
periodNoA preset period, in the site's time zone. Leave out for the tool's default, or give from and to instead.
filtersNoVisits that match every filter (AND). Each dimension at most once.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description usefully names the metrics returned, which compensates for the absent output schema. It does not disclose default period behavior, pagination or whether funnels are actually returned when not requested.

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?

The first clause is information-dense and front-loaded, but it crams five metrics into one semicolon-chained sentence. The final sentence about funnels is not clearly connected to the goals purpose and risks misdirecting the agent. Structure is serviceable but not clean.

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 six parameters, a nested filter object and no output schema, the description does cover the returned metrics, which is the main gap. However it omits the default period, does not explain what 'completions' versus 'converting visitors' means dimensionally, and leaves the funnel claim unexplained relative to the get_funnels sibling.

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 including the nested filter object is documented in the schema itself, which sets the baseline at 3. The description adds only a small gloss on `goal` ('for its properties' breakdown') and says nothing about how period interacts with from/to beyond what the schema already states.

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 and scope: goals completed within a period, with completions, converting visitors, conversion rate and revenue of converters. That is a clear read purpose. The trailing sentence 'Lists the site's funnels' muddies it, since a sibling named get_funnels exists and the description does not explain how the two differ.

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 only conditional guidance is 'give `goal` for one goal's properties', which tells the agent how to narrow the result but not when to pick this tool over get_funnels or get_breakdown. There are no exclusions or prerequisites stated. Usage is implied rather than spelled out.

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