search_committee_documents

Pack: committee-releases · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)

No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/search_committee_documents for the schema, then POST the same URL with its arguments for the data.

Find documents published by a congressional committee on its own website — press releases,

Parameters

NameTypeRequiredDescription
querystringnoKeywords matched against document headlines, all of which must appear, e.g. “subpoena FBI”.
committeestringnoWhich committee: “house-oversight”, “hsgac”, or “all” (default). Also accepts loose names
doc_typestringnoWhat to search: “releases”, “letters”, “reports”, “hearings”, “markups”, “documents”
sincestringnoOnly documents updated on or after this date, YYYY-MM-DD
limitnumbernoResults to return (default 20, max 100)

Example call

Arguments

{
  "query": "subpoena",
  "limit": 5
}

curl

curl -X POST https://gateway.pipeworx.io/committee-releases/mcp \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_committee_documents","arguments":{"query":"subpoena","limit":5}}}'

TypeScript (@pipeworx/sdk)

import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();

const result = await pipeworx.call('search_committee_documents', {
  "query": "subpoena",
  "limit": 5
});

More examples

{
  "committee": "house-oversight",
  "doc_type": "letters",
  "limit": 5
}

Connect

Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://pipeworx.io/mcp"
    }
  }
}
Connect to just the committee-releases pack
{
  "mcpServers": {
    "committee-releases": {
      "url": "https://gateway.pipeworx.io/committee-releases/mcp"
    }
  }
}

See Getting Started for client-specific install steps.

Regenerated from source · build October 28, 2026