Skip to main content
Glama

list_pipeline_search_history

Retrieves paginated search history for a pipeline, including queries, results, timing, status, feedback, and notes. Use after cursor for pagination and optional filters to narrow results.

Instructions

Retrieves search history for a specific pipeline with pagination.

Returns past searches run with the given pipeline. Each entry includes the search query (request.query), results (response), timing (time/duration), status, user info, feedback, labels, and note.

Search history is archived ~30 minutes after a search runs and is then available via this endpoint.

Use the after parameter with next_cursor from the response to fetch the next page. :param pipeline_name: Name of the pipeline to get search history for. :param limit: Maximum number of entries to return per page (default 10, max 1000). :param after: ISO-8601 timestamp cursor to fetch entries older than this point. Pass the value 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: "created_at ge 2024-01-01T00:00:00Z" or "status eq 'failed'". :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 search history entries or 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 fully discloses important behaviors: archiving delay of ~30 minutes, output stored and returned as object ID for use with object store tools, and pagination mechanics.

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 well-structured with front-loaded purpose and detailed parameter sections. It is somewhat lengthy but each sentence adds value. Could be slightly more concise but overall effective.

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?

Given no output schema and no annotations, the description thoroughly covers input parameters, output structure (including fields in each entry), pagination, and how to use object IDs. It also mentions error handling briefly.

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?

The input schema has 0% coverage, but the description provides extensive documentation for all 6 parameters including defaults, examples, supported fields for query_filter, and enum values for sort_field and sort_order.

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 it retrieves search history for a specific pipeline with pagination. It distinguishes itself from the sibling tool 'list_search_history' by focusing on pipeline-specific history.

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

Usage Guidelines4/5

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

The description explains the context for using this tool (getting search history for a pipeline) and provides detailed pagination guidance. However, it does not explicitly state when to use it versus alternatives like 'list_search_history'.

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