Skip to main content
Glama
Sign In
deepset-ai

deepset-mcp

Official
by deepset-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

list_pipeline_search_history

Retrieves paginated search history for a specific pipeline so you can review past queries, results, timing, status, user feedback, and notes.

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.

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

NameRequiredDescriptionDefault
afterNo
limitNo
sort_fieldNocreated_at
sort_orderNoDESC
query_filterNo
pipeline_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.9
    • addedInput schema / properties / sort_field
      Added value: +{
+  "default": "created_at",
+  "enum": [
+    "created_at",
+    "query",
+    "duration",
+    "feedbacks/score"
+  ],
+  "title": "Sort Field",
+  "type": "string"
+}
    • addedInput schema / properties / sort_order
      Added value: +{
+  "default": "DESC",
+  "enum": [
+    "ASC",
+    "DESC"
+  ],
+  "title": "Sort Order",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the per-entry payload shape (query, response, timing, status, user, feedback, labels, note), pagination semantics with the 10/1000 limit bounds, sort defaults, and the non-obvious side effect that results are auto-stored as an object reference (e.g. @obj_123) reusable via object-store tools. It omits permission/auth requirements, which is the main remaining gap.

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?

Front-loaded summary of what is fetched, followed by return shape, pagination instruction, then per-parameter notes — every section is scannable. The trailing object-store paragraphs are boilerplate but carry real behavioral information, so the length is mostly earned, though the query_filter field list is long.

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?

With no output schema and no annotations, the description supplies both the return-value shape and the storage/reference behavior, plus complete parameter semantics. An agent has everything needed to call it correctly and interpret the response.

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 description coverage is 0%, so the description must compensate and it does for all six parameters: limit default and max, after as an ISO-8601 cursor taken from next_cursor, sort_field's allowed values plus default, sort_order direction semantics, and an enumerated field list with example OData expressions for query_filter. This is meaningfully richer than the bare schema.

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 and resource with a clear scope qualifier: retrieves search history for a specific (named) pipeline, with pagination. An agent can tell what it fetches, but the description never differentiates it from the sibling list_search_history, which by name covers a very similar surface.

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

Usage Guidelines3/5

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

Usage is implied rather than stated: 'Use the after parameter with next_cursor' tells how to paginate, and pipeline_name implies the scoping condition, but there is no explicit when-to-use-this-vs-list_search_history guidance and no stated prerequisites or exclusions.

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