get_committee_document

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/get_committee_document for the schema, then POST the same URL with its arguments for the data.

Read a committee document page: its headline, publication date, the text the committee published,

Parameters

NameTypeRequiredDescription
urlstringyesFull committee document URL, as returned by search_committee_documents

Example call

Arguments

{
  "url": "https://oversight.house.gov/release/chairman-comer-issues-two-subpoenas-to-leon-black/"
}

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":"get_committee_document","arguments":{"url":"https://oversight.house.gov/release/chairman-comer-issues-two-subpoenas-to-leon-black/"}}}'

TypeScript (@pipeworx/sdk)

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

const result = await pipeworx.call('get_committee_document', {
  "url": "https://oversight.house.gov/release/chairman-comer-issues-two-subpoenas-to-leon-black/"
});

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