Skip to main content
Glama
Sign In
segment-mcp

segment-mcp

by pedromfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_tracking_plan

Fetch a tracking plan by ID to review event schemas and data collection rules without modifying the Segment workspace.

Instructions

Get a single tracking plan by id.

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": {
      "trackingPlanId": "<trackingPlanId>"
    },
    "name": "get_tracking_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackingPlanIdYesThe tracking plan id.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description bears the full behavioral burden, yet it discloses nothing about failure behavior (e.g., not-found), authentication needs, or what is returned. It essentially restates the tool name.

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 short sentence with no wasted words and the core action front-loaded. It is efficient, though its terseness is partly under-specification rather than disciplined brevity.

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?

For a low-complexity single-parameter lookup with no output schema, the description is minimally sufficient. It nevertheless omits any note on error handling or return content, which an agent would benefit from given there are no annotations or output schema.

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 100% and the single parameter is documented in the schema as 'The tracking plan id.' The description adds no format, source, or constraint details beyond that, so the baseline of 3 applies.

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?

States a specific verb (get) and resource (tracking plan) and scopes it to a single item by id, which separates it from list_tracking_plans. It does not explicitly name the sibling list tool, so it falls short of 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 Guidelines2/5

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

The phrase 'by id' implies an id must be known, but there is no statement of when to use this over list_tracking_plans or what to do if the id is unknown. No alternatives or exclusions are named.

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

Deploy Server

Other Tools