Skip to main content
Glama
Sign In
buildin-mcp

buildin-mcp

by ekho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search Buildin pages

buildin_search

Search across all accessible pages with keywords or retrieve recently-updated pages. Returns paginated page objects.

Instructions

Search across all pages the bot has access to. Returns a paginated list of page objects. query is free-form; empty string returns recently-updated pages.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "buildin_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryNoSearch keywords. Empty/omitted lists recent pages.
start_cursorNo
page_sizeNo1..100, default 10.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.1

TDQS

C2.9/5.0
Behavior2/5

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

No annotations provided, so description must carry behavioral info. It only says 'returns a paginated list' but lacks details on sorting, permissions, rate limits, or result structure beyond basic pagination.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two clear sentences, front-loaded with the main purpose. Could be slightly more structured but efficient overall.

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

Completeness2/5

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

With no output schema and moderate parameter count, the description is insufficient. It doesn't explain the structure of returned page objects, ordering, or limits on results, leaving gaps for correct use.

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 coverage is 67%, but the description only adds minimal extra info about query being free-form. The start_cursor parameter is left undocumented in both schema and description, forcing the agent to guess its purpose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches across all pages and returns a paginated list. It distinguishes from get_page and query_database, but not explicitly from buildin_search_and_fetch.

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?

Mentions that query is free-form and empty returns recent pages, giving some usage context. However, no guidance on when to use this vs. sibling tools or 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