Skip to main content
Glama
Sign In
buildin-mcp

buildin-mcp

by ekho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Create Buildin database

buildin_create_database

Create a new Buildin.ai database under a specified page parent, requiring at least one title property, with an option to make it inline.

Instructions

Create a new Buildin.ai database under a page parent. Must include at least one property of type 'title'. Set is_inline=true for inline databases.

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": {
      "parent": "<parent>",
      "title": "<title>",
      "properties": "<properties>"
    },
    "name": "buildin_create_database"
  }
}

Input Schema

NameRequiredDescriptionDefault
parentYesUsually a page parent: { page_id: '...' }.
titleYesArray of rich-text runs.
propertiesYesMap of property name -> schema definition. At least one property of type 'title' must be present.
iconNoIcon: emoji or external url. Both discriminator-less and typed forms accepted to match Buildin examples.
coverNoCover image (external url only).
is_inlineNotrue for inline databases embedded on a page, false for full-page databases.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It does not mention permissions, side effects, idempotency, or what happens on success/failure. The only behavioral information is the requirement for a title property and the is_inline flag, which are more like input constraints than behavioral traits.

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 three concise sentences that front-load the main action (create database) and then add key constraints. No redundant or extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description covers the essential constraints for creation (parent, title property, is_inline) but does not describe the return value (no output schema) or any error conditions. Given the tool's complexity (6 parameters, nested objects), the description is somewhat brief but adequate for a basic create operation.

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 description coverage is 100%, but the description adds practical meaning beyond the schema by clarifying that the parent should be a 'page parent', emphasizing that properties must include a title type, and noting that is_inline=true is for inline databases. This provides extra guidance that the schema's individual property descriptions do not.

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 action (Create) and resource (Buildin.ai database under a page parent), with specific constraints (must include at least one title property, is_inline for inline databases). This distinguishes it from sibling tools like buildin_create_page, which create pages, not databases.

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 provides basic context on where to create (under a page parent) and key constraints (title property, is_inline), but does not explicitly state when to use this tool versus alternatives like query_database or update_database. It offers implied usage but no exclusions or alternative guidance.

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