Skip to main content
Glama
Sign In
segment-mcp

segment-mcp

by pedromfs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

list_tracking_plans

Retrieve all tracking plans in a Segment workspace to inspect event schemas and data governance settings without making changes.

Instructions

List all tracking plans in the workspace.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add useful scope information ('all', 'in the workspace', implying no filtering), but it says nothing about pagination, result ordering, or permission requirements for a tool whose reads could be workspace-wide.

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?

A single front-loaded sentence with no filler, no redundancy with the title, and immediate statement of resource and scope.

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 zero-parameter list tool this is close to sufficient, but with no output schema and no annotations, the description could have said something about the shape of the result set or how large result sets are returned. Adequate, with a visible gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so the baseline of 4 applies; there is no parameter semantics for the description to clarify, and it does not confuse the matter.

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 pairs a specific verb with a specific resource ('List all tracking plans') and scopes the result to the workspace, so an agent can distinguish it from get_tracking_plan. It stops short of explicitly routing the agent away from the singular sibling, which is what a 5 would require.

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 statement of when to use this tool versus list_sources, list_functions, list_destinations, or get_tracking_plan. Enumeration is loosely implied by 'List all', but no alternatives, prerequisites, or exclusions are given.

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