Skip to main content
Glama
Sign In
buildin-mcp

buildin-mcp

by ekho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Read a Buildin page as Markdown

buildin_get_page_markdown

Fetch all child blocks from a page and convert them to Markdown. Use to quickly summarize or ingest page content.

Instructions

Fetch every child block of a page (walks pagination, follows has_children) and render the result as Markdown. Useful for quickly summarising or ingesting a 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": "buildin_get_page_markdown"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYesPage id whose content to read.
max_depthNoHow deep to recurse into child blocks (default 2).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.4/5.0
Behavior4/5

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

The description discloses key behaviors: walking pagination, following has_children, and rendering Markdown. With no annotations, this is sufficient transparency. It could mention that the operation is read-only, but that is implied.

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?

The description is two sentences, each adding distinct value. It is front-loaded with the action and purpose, with no wasted words. Ideal conciseness.

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?

The description explains pagination and recursion, which are important for a tool that traverses blocks. It does not describe the output format beyond Markdown, but since there is no output schema, this suffices. Could be more complete, but adequate.

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?

The input schema fully describes both parameters. The description adds behavioral context: 'walks pagination, follows has_children' and clarifies the meaning of max_depth with a default value. This provides added value beyond the schema.

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 the tool fetches child blocks and renders them as Markdown, which is a specific resource and output format. It distinguishes from siblings like buildin_get_page (likely JSON) and buildin_get_block_children (raw blocks).

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 provides a clear use case ('quickly summarising or ingesting a page') and implies when to use it over alternative tools. However, it does not explicitly state when not to use it or list alternative tools for comparison.

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