KrystalView Analytics

Get Campaign Sessions

get_campaign_sessions

Read-onlyIdempotent

List sessions attributed to a specific marketing campaign.

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": {
      "campaign": "<campaign>"
    },
    "name": "get_campaign_sessions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Maximum results to return.
`offset`	No	Pagination offset.
`campaign`	Yes	UTM campaign name.

Output Schema

Name	Required	Description	Default
`data`	Yes	Visitor sessions attributed to the requested UTM campaign.
`meta`	Yes	Site and rate-limit metadata for the current MCP call.

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 10, 2026

TDQS

B3.3/5.0

Behavior2/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false. The description adds no behavioral details beyond 'list', such as pagination behavior or rate limits, failing to add value beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Single sentence with no wasted words. Front-loaded with purpose. Efficient for a simple listing tool.

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 output schema and annotations, the basic function is covered. However, given 12 sibling tools, more context on how this differs from 'get_sessions' or when to use pagination would improve completeness.

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 baseline is 3. The description does not add any parameter context beyond schema, which is acceptable as schema fully documents the three parameters.

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 clearly states 'List sessions attributed to a specific marketing campaign' with a specific verb and resource. It distinguishes itself from sibling tools like 'get_sessions' (all sessions) and 'get_session_detail' (single session) by specifying campaign attribution.

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?

No explicit guidance on when to use this tool versus alternatives. While the purpose implies use for campaign-related sessions, it doesn't mention when not to use it or suggest other tools like 'get_campaign_summary' for aggregated data.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All KrystalView Analytics tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.