Skip to main content
The server exposes read and write tools, plus server_info. Each one wraps a single REST API v2 operation and takes the same arguments as the endpoint behind it, so the endpoint reference is the place to look for full response schemas. The Stage column shows each tool’s release stage (Alpha, Beta, or Stable), inherited from the REST operation it wraps. See API version stages for what each stage means for reliability and breaking changes. The Access column shows whether a tool reads data, writes data, or is destructive, matching the annotations MCP clients use to decide when to ask for approval. See conventions for the pagination, span limit, timeout, and error rules shared across every tool below.

Annotations

Datasets

Evaluators

Experiments

Integrations

Monitors

Organizations

Projects

Prompts

Server info

Spaces

Tasks

Traces and spans

Not exposed

The server does not expose API keys, users, roles, webhooks, audit logs, or the operations that add and remove tags. Tags are read-only through the list_*_tags tools.