Skip to main content
Glama

list_pipeline_traces

Browse Haystack pipeline run summaries with status, timing, and failure details. Use query_id to fetch full execution traces for debugging.

Instructions

Lists Haystack pipeline run trace summaries for a specific pipeline.

Returns one lightweight summary per query run — query_id, query text, status, timing (duration_s, created_at), and failure details if the run failed. Summaries do not include spans or logs. Use this to browse runs, find slow or failed queries, then pass a query_id to get_pipeline_trace for the full execution trace (spans with essential tags such as component type), get_pipeline_trace_span_tags for a single span with full tags (including input/output), or get_pipeline_trace_logs for the logs of the trace.

Use the after parameter with next_cursor from the response to fetch the next page. :param pipeline_name: Name of the pipeline to retrieve traces for. :param limit: Maximum number of trace entries to return per page (default 10). :param after: ISO-8601 timestamp cursor from next_cursor on the previous response. :param query_filter: An OData filter expression to narrow down results. Supported fields: query, client_source_path, pipeline_version_id, answer, api_key, created_at, created_by, tags/tag_id, feedbacks, feedbacks/score, feedbacks/comment, feedbacks/bookmarked, session_id, search_session_id, feedbacks/result_id, request/filters, request/params, duration, labels, status, note. Example: "status eq 'failed'" or "created_at ge 2024-01-01T00:00:00Z". :param sort_field: Field to sort results by. One of: created_at, query, duration, feedbacks/score. Defaults to created_at. :param sort_order: Sort direction — ASC (oldest first) or DESC (newest first). Defaults to DESC. :returns: Paginated list of pipeline trace summaries or an error message.

The output is automatically stored and can be referenced in other functions. Returns a formatted preview with an object ID (e.g., @obj_123). Use the object store tools in combination with the object ID to view nested properties of the object. Use the returned object ID to pass this result to other functions.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
afterNo
limitNo
sort_fieldNocreated_at
sort_orderNoDESC
query_filterNo
pipeline_nameYes
Behavior5/5

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

With no annotations, the description carries full responsibility. It discloses what the summaries include (query_id, status, timing, failure details) and what they exclude ('do not include spans or logs'), and explains that the output is automatically stored and returns an object ID for later reference.

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?

The description is front-loaded with purpose and return semantics, then parameter docs. It is longer than minimal, but the length is justified by the parameter richness and usage guidance; no sentence is wasted.

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

Completeness5/5

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

For a tool with six parameters, no output schema, and no annotations, the description fully covers return values, pagination, filtering, sorting, object ID handling, and differentiates from related tools.

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

Parameters5/5

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

Schema coverage is 0%, but the description compensates fully with :param docs for all six parameters, including defaults, supported filter fields, enum values for sort_field, and OData filter examples.

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 opens with a specific verb+resource: 'Lists Haystack pipeline run trace summaries for a specific pipeline.' It clearly distinguishes itself from siblings like get_pipeline_trace, get_pipeline_trace_span_tags, and get_pipeline_trace_logs by stating it returns lightweight summaries without spans or logs.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicit usage guidance is provided: 'Use this to browse runs, find slow or failed queries, then pass a query_id to get_pipeline_trace for the full execution trace...' It also documents pagination via 'after' and 'next_cursor', and mentions alternatives for spans, tags, and logs.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deepset-ai/deepset-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server