Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

get_pipeline_history

Read-onlyIdempotent

Retrieve execution history for a saved pipeline to see past runs, article counts, and which articles are new or removed compared with the previous run.

Instructions

Get execution history for a saved pipeline.

Shows past execution results with diff analysis: which articles are new compared to the previous run.

Args: name: Name of the saved pipeline. limit: Maximum number of history entries to return (default: 5).

Returns: Execution history with date, article count, new/removed articles, status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.7.7
    • addedInput schema / properties / limit / anyOf
      Added value: +[
+  {
+    "default": 5,
+    "maximum": 100,
+    "minimum": 1,
+    "title": "Limit",
+    "type": "integer"
+  },
+  {
+    "description": "ASCII decimal integer; the integer branch's bounds apply after conversion.",
+    "maxLength": 32,
+    "pattern": "^[ \\t\\r\\n]*-?(?:0|[1-9][0-9]*)[ \\t\\r\\n]*$",
+    "type": "string"
+  }
+]
    • removedInput schema / properties / limit / maximum
      Removed value: -100
    • removedInput schema / properties / limit / minimum
      Removed value: -1
    • removedInput schema / properties / limit / type
      Removed value: -"integer"
  2. Changed7 schema fields changedv0.7.2
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / limit / maximum
      Added value: +100
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • addedInput schema / properties / name / maxLength
      Added value: +64
    • addedInput schema / properties / name / minLength
      Added value: +1
    • addedInput schema / properties / name / pattern
      Added value: +"^[a-z0-9](?:[a-z0-9_-]{0,63})$"
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "result": {
-      "title": "Result",
-      "type": "string"
-    }
-  },
-  "required": [
-    "result"
-  ],
-  "title": "get_pipeline_historyOutput",
-  "type": "object"
-}New value: +null
  3. First observedv0.5.16

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds genuine behavioral value beyond that: it explains the diff-analysis semantics (new/removed articles vs. the previous run) and the shape of returned data, which is not derivable from annotations.

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 with a one-line purpose, then Args and Returns sections. Every element earns its place; the only minor overhead is the conventional docstring scaffolding, which is still efficient and scannable.

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

Completeness4/5

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

With no output schema, the description fills the gap by describing the return contents (date, article count, new/removed articles, status). Annotations cover the safety profile and both parameters are addressed, making it largely complete, though the name-pattern constraint and absence of pagination guidance are minor gaps.

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

Parameters3/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 carry the load. It documents both parameters, including the limit default of 5, which the schema also encodes. However, it does not explain the name pattern (lowercase slug, max 64 chars) or the limit bounds (1-100), leaving format constraints undocumented.

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 states a specific verb+resource ('Get execution history for a saved pipeline') and clarifies scope ('for a saved pipeline'), which distinguishes it from pipeline-management siblings like save_pipeline, list_pipelines, and delete_pipeline. It does not explicitly name any sibling, but the read-only history focus is unambiguous.

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?

No explicit when-to-use guidance or alternatives are given. The phrase 'for a saved pipeline' implies the pipeline must already exist, but the description never says to use list_pipelines first, nor when this is preferred over any other tool. Usage is only weakly inferable.

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