Skip to main content
Glama

Tally by Outpost

Funnels

get_funnels
Read-onlyIdempotent

The site's funnels with each step's visitors, conversion from the step before and from the first, and drop-off; or one funnel with funnel.

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_funnels"
  }
}

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.
siteNoThe site's id. Optional: the API key's site is the one read.
funnelNoOne funnel's id (from get_goals); leave out for all of them.
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

A3.5/5.0
Behavior3/5

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

Annotations already establish readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description's real contribution is disclosing the shape of the result (per-step visitors, step-to-step and first-step conversion, drop-off), which matters because no output schema exists. It adds nothing about default date range behavior, result limits, or how steps are ordered.

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?

One dense sentence that front-loads the resource and enumerates the returned measurements with no filler. The semicolon-separated single-funnel mode is compact but reads slightly like a run-on, which keeps it from a 5.

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

Completeness4/5

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

All six parameters are optional and fully documented in the schema, and the description fills the one real gap by explaining what the tool returns, since there is no output schema. What is missing is modest: default period behavior and how many funnels or steps come back for an unscoped call.

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%, including the `funnel` parameter already stating 'leave out for all of them', so the description's funnel clause largely repeats the schema. The date/period/filter semantics are left entirely to the schema, which is acceptable at this coverage level but adds no extra meaning.

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 the concrete resource (funnels) and the exact payload an agent gets back: per-step visitors, conversion from the previous step and from the first, and drop-off. It also distinguishes the two shapes (all funnels vs a single one). It stops short of contrasting itself with adjacent analysis siblings like get_goals or get_purchase_paths, so a 4 rather than a 5.

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?

Usage is only implied through the 'or one funnel with `funnel`' clause, which tells the agent how to switch scope but not when to prefer this tool over sibling analyses. There are no exclusions, no prerequisites, and no statement about what the default call returns when everything is omitted.

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