Skip to main content
Glama
Sign In
Billboardbug MCP

Billboardbug MCP

by bgaut007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Search deals

search_deals
Read-only

Search BillboardBug public deals by text to find relevant offers; requires an API key and at least 3 characters.

Instructions

Search BillboardBug deals by text (min 3 characters). Requires an API key.

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": {
      "search": "<search>"
    },
    "name": "search_deals"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
offsetNo
searchYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.1

TDQS

B3.1/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe read. The description adds the API-key requirement and the minimum query length, which is modest added value, but says nothing about result ordering, pagination behavior, or rate limits.

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 short sentences, front-loaded with the core action and no filler. It is efficient, though it spends words on a constraint the schema already enforces rather than on the undocumented parameters.

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?

For a 3-parameter tool with no output schema and no schema descriptions, the definition is thin: paging parameters and result shape/pagination semantics are left entirely unaddressed, so an agent cannot confidently bound or page a query.

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 description coverage is 0%, so the description must carry parameter meaning. It only restates the min-3-character rule already enforced by minLength on 'search' and never explains limit (max 100) or offset, leaving two of three parameters undocumented anywhere.

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?

States a specific verb (search) and resource (deals) plus the scope of matching (by text, min 3 characters). It distinguishes itself reasonably from list_my_deals by being a text query, though it never names that sibling explicitly.

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 verb 'search' and the API-key prerequisite is noted, but there is no explicit when-to-use guidance, no mention of when to prefer list_my_deals or list_categories, and no pagination advice for a tool that exposes offset/limit.

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