Skip to main content
Glama
Sign In

BuiltWith

by io.github.builtwith
OverviewDiscussionsAdmin

keywords-search-api

Keyword Search API — find websites containing a specific keyword. Returns a list of matching domains and a NextOffset value for pagination. Costs API credits per query.

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": {
      "keyword": "<keyword>"
    },
    "name": "keywords-search-api"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults per request (16–1000, default 100)
offsetNoDomain name from the previous response's NextOffset for pagination
keywordYesThe keyword to search for (e.g. 'perfume')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations only declare readOnly=false, destructive=false and openWorld=false, so the description materially adds that each query consumes API credits and that results are paginated via a NextOffset value. That cost and pagination context is exactly what an agent needs before calling and is not visible in the structured fields.

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?

Three short sentences, front-loaded with purpose, then return shape, then cost. Only the leading "Keyword Search API" label largely duplicates the tool name and could be dropped.

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?

With no output schema, the description correctly explains the return shape and pagination mechanism, which is the main completeness risk for this tool. The remaining gap is that the credit cost is stated qualitatively without any magnitude, and sibling selection is unaddressed.

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 all three parameters carry descriptions, including offset referencing NextOffset. The description's pagination sentence largely restates what the schema already documents, adding little new parameter meaning.

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 uses a specific verb and resource ("find websites containing a specific keyword") and states what is returned (matching domains plus NextOffset). It does not distinguish this tool from the similarly named siblings such as x402-keywords-search-api or keywords-api, so it stops 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 keyword-search framing and the mention that each query costs API credits, which nudges the agent to use it deliberately. There is no explicit statement of when to prefer this over the keyword-related siblings 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.

All BuiltWith toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources