Skip to main content
Glama
Sign In
killbottleneck-mcp

killbottleneck-mcp

Official
by tengolabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_page

Retrieve a page's metadata and full HTML by page_id to inspect content before making updates; use the page_id from list_pages.

Instructions

Read one page (page_id from list_pages): its metadata and the full HTML. Read it before changing a page with update_page.

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": {
      "page_id": "<page_id>"
    },
    "name": "get_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A4.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It does well on output content by naming metadata plus full HTML, but says nothing about permissions, behavior on an unknown or deleted page_id, or whether large HTML payloads are truncated.

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 short sentences with zero filler. The return content is front-loaded and the workflow constraint follows, so an agent can stop reading after the first line if it only needs to know what the tool returns.

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 single-parameter read tool with no output schema, the description covers the essentials: what it returns and when to call it. The only meaningful gap is failure behavior for an invalid page_id, which is minor relative to the tool's simplicity.

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 0%, so the single parameter is undocumented in structured fields. The description compensates by explaining that page_id is a page identifier sourced from list_pages, which is the key semantic an agent needs; format details remain unstated but the origin guidance is the substantive part.

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?

States a specific verb and resource ("Read one page") and immediately specifies what comes back: "its metadata and the full HTML." It also anchors the identifier's origin ("page_id from list_pages"), so an agent can distinguish this retrieval tool from list_pages and update_page without opening any schema.

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

Usage Guidelines5/5

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

Gives an explicit prerequisite chain: obtain page_id from list_pages, and call this before mutating with update_page. Both the upstream alternative and the downstream dependency are named with the condition that selects them, leaving nothing to inference.

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