plaid-devx-mcp

Fetch a docs page as Markdown

plaid_docs_fetch

Fetch any Plaid documentation page as Markdown, with configurable truncation and offset for reading long content in chunks.

Instructions

Every plaid.com/docs page is also served as Markdown at /index.html.md. Returns that text, truncated to max_chars, optionally starting at an offset for paging.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "plaid_docs_fetch"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	A plaid.com/docs URL, e.g. https://plaid.com/docs/transactions/
`offset`	No
`max_chars`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 15, 2026

TDQS

A4.4/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 discloses key behaviors: the Markdown source endpoint, truncation by max_chars, and offset-based paging. It does not mention error handling, auth, or rate limits, but the core read-only behavior is transparent.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the core action and source, followed by concise parameter behavior. No filler; every sentence contributes.

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?

For a straightforward fetch tool with three simple parameters and no output schema, the description covers the source, retrival mechanism, and both optional parameters. It lacks explicit notes on error cases or unsupported URLs, but the essentials for correct invocation are all present.

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

Parameters4/5

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

Schema coverage is only 33% (url is documented). The description compensates by explaining that max_chars truncates the returned text and offset supports paging, adding semantic value beyond the schema's field descriptions. It could more precisely define character units, but the intent is clear.

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 a specific verb ('Fetch') and resource ('a docs page as Markdown'), and explains the underlying mechanism via index.html.md. This clearly distinguishes it from siblings like plaid_docs_search, which would find pages rather than fetch a page content.

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 says 'Every plaid.com/docs page' establishes the scope of applicability and the behavior for paging/truncation. It does not explicitly identify sibling alternatives or exclusions, but the usage context is clear enough for an agent to know when to invoke this tool.

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