Skip to main content
Glama
Sign In
buildin-mcp

buildin-mcp

by ekho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Get Buildin page

buildin_get_page

Retrieve a Buildin.ai page by its ID and return its properties, icon, cover, parent, and URL.

Instructions

Retrieve a Buildin.ai page by its id. Returns the page object including properties, icon, cover, parent and url.

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"
  }
}

Input Schema

NameRequiredDescriptionDefault
page_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations provided, the description must fully disclose behavioral traits. It describes the return object but doesn't mention read-only nature, error handling, or authorization requirements, which are important for a simple read operation.

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 long, front-loaded with purpose, and contains no extraneous information. Every word contributes value.

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?

Given the single parameter and no output schema, the description covers the return object details adequately. However, it could be more complete by mentioning read-only behavior or common error scenarios.

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

Parameters2/5

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

Schema description coverage is 0% for the only parameter 'page_id', and the description adds no additional meaning beyond 'by its id'. It does not provide format, constraints, or examples.

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 'Retrieve a Buildin.ai page by its id', specifying a specific verb and resource. It distinguishes from sibling tools like buildin_get_block and buildin_get_database by focusing on pages.

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

Usage Guidelines3/5

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

The description implies usage for retrieving a page by ID but provides no explicit guidance on when to use this tool versus alternatives, nor any context on when not to use it.

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