Skip to main content
Glama
Sign In
buildin-mcp

buildin-mcp

by ekho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Update Buildin block

buildin_update_block

Update a block's content or state, including text, to-do status, or archiving.

Instructions

Update a block's content or state. For text blocks, pass data: { rich_text: [...] }. To toggle a to_do, pass data: { checked: true }. To archive, pass archived: true.

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": {
      "block_id": "<block_id>"
    },
    "name": "buildin_update_block"
  }
}

Input Schema

NameRequiredDescriptionDefault
block_idYesBuildin object ID (UUID-like).
dataNoPartial data for the block's type-specific payload.
archivedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A4.2/5.0
Behavior3/5

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

With no annotations, the description discloses mutation behaviors (update, toggle, archive) but omits side effects (e.g., versioning, permissions) and error handling. Adequate but not thorough.

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?

Three sentences, each purposeful: general purpose, text block example, to_do and archive examples. No redundant text.

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?

Covers the most common updates (text, to_do, archive) but does not mention other block types or error scenarios. Given the absence of output schema, it is reasonably complete for a typical agent.

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 description adds meaning beyond the schema by explaining how to use the data and archived parameters for common tasks. The schema coverage is 67%, and the description compensates well, though it does not cover all possible block types.

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 it updates a block's content or state, and provides specific examples (text blocks, to_do toggle, archive). This distinguishes it from sibling tools like delete or page updates.

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 examples guide when to use specific parameters (e.g., for text blocks vs. to_do). However, it lacks explicit mention of when not to use this tool compared to update_page or update_database.

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