Skip to main content
Glama
Sign In
buildin-mcp

buildin-mcp

by ekho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Archive or unarchive Buildin page

buildin_archive_page

Set a page as archived in Buildin.ai; use archived=false to restore it.

Instructions

Convenience wrapper over update_page: sets archived=true by default (pass archived=false to restore). Buildin.ai does not expose hard-delete for pages.

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

Input Schema

NameRequiredDescriptionDefault
page_idYes
archivedNoDefaults to true (archive). Pass false to unarchive.

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?

With no annotations, description carries full burden; it discloses default action, reversibility, and absence of hard-delete. Could mention idempotency or side effects, but sufficient for simple tool.

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 concise sentences with no fluff. Front-loaded with key information, earning each word.

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?

Complete for a simple wrapper: explains purpose, default, and limitation. Lacks mention of idempotency or error scenarios, but not critical for this tool.

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?

Adds meaning to archived parameter (defaults and restore) beyond schema's description and default. For page_id, it's implied through context but no extra detail. Compensates for 50% schema coverage.

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?

Description clearly states verb (archive/unarchive), resource (page), and positions as convenience wrapper over update_page. Distinguishes from sibling update_page by adding context about no hard-delete.

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?

Explicitly explains default behavior (archived=true) and how to reverse (pass archived=false). Implicitly suggests using update_page for other updates, but lacks explicit when-not or alternative list.

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