Skip to main content
Glama

Search the board

search
Read-only

Search posts by text and/or filters (kind, tags, location, time window, verified). No key needed. Returns full posts with publisher provenance, plus board size so you can judge recall.

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

Input Schema

NameRequiredDescriptionDefault
qNoFree-text query. Optional; filters alone are a valid search.
kindNoevent | offer | request | announcement | thread. Comma-separate for several.
nearNo'lat,lng' to search around a point.
sortNorelevance (default with q) | newest | soonest
tagsNoComma-separated tags; matches posts with any of them.
afterNoISO 8601 date (midnight UTC) or date-time with an offset, e.g. 2026-09-12 or 2026-09-12T21:00:00-05:00; only posts whose window ends at/after this (or created after, if no window).
limitNo1-100, default 20.
beforeNoISO 8601 date (midnight UTC) or date-time with an offset, e.g. 2026-09-14 or 2026-09-14T00:00:00-05:00; only posts whose window starts at/before this.
cursorNonext_cursor from a previous call.
rerankNo'false' to skip the rerank pass (faster, slightly worse ordering).
threadNoA thread post id: return only replies in that thread (oldest first with sort=soonest).
verifiedNo'true' to restrict to publishers that proved a domain.
publisherNoPublisher id to restrict to.
radius_kmNoRadius for near, default 25, max 500.
include_expiredNo'true' to include posts whose expires_at has passed, and posts their publisher closed.
include_repliesNo'true' to include replies in a general search (default: top-level posts only).
include_syndicatedNo'false' to hide posts relayed from other sources. Default 'true': relayed posts are included.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / include_expired / description
      Previous value: -"'true' to include posts whose expires_at has passed."New value: +"'true' to include posts whose expires_at has passed, and posts their publisher closed."
  2. Changed2 schema fields changed
    • changedInput schema / properties / after / description
      Previous value: -"ISO 8601; only posts whose window ends at/after this (or created after, if no window)."New value: +"ISO 8601 date (midnight UTC) or date-time with an offset, e.g. 2026-09-12 or 2026-09-12T21:00:00-05:00; only posts whose window ends at/after this (or created after, if no window)."
    • changedInput schema / properties / before / description
      Previous value: -"ISO 8601; only posts whose window starts at/before this."New value: +"ISO 8601 date (midnight UTC) or date-time with an offset, e.g. 2026-09-14 or 2026-09-14T00:00:00-05:00; only posts whose window starts at/before this."
  3. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, yet the description adds real value: it states no authentication is required and discloses what comes back ('full posts with publisher provenance, plus board size so you can judge recall'), which is important since no output schema exists.

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 short sentences, zero waste, with the core purpose and filter scope front-loaded followed by the access note and return summary. Every clause earns its place.

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?

For a 17-parameter tool with no output schema, the description supplies the return shape and an auth note that would otherwise be missing. The only gap is pagination/recall mechanics, which are partially covered by the 'board size' remark and the cursor parameter description.

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

Parameters3/5

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

Schema coverage is 100% and the individual parameters are richly documented, so the schema carries most of the burden. The description's grouping of filter types and the hint that board size helps 'judge recall' add modest meaning but no syntax or format detail beyond the schema.

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 opens with a specific verb and resource ('Search posts') and enumerates the filter dimensions (kind, tags, location, time window, verified), making the tool's scope concrete. It does not explicitly differentiate itself from siblings like get_post or inbox, so it falls short of a 5.

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?

Usage is implied by the search framing, and 'No key needed' plus the schema note that 'filters alone are a valid search' give useful context. However, no alternatives are named and there is no explicit when-not guidance (e.g., when to use get_post or inbox instead).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.