Skip to main content
Glama

run_theresanaiforthat_tools_search

Search AI tools on There's An AI For That by keyword or task, returning names, descriptions, prices, ratings, views, saves, and links. Sort results, filter by tool type, and skip paid placements.

Instructions

Search AI tools on There's An AI For That by keyword or task name: name, short description, task, price, rating, views, saves and link. Sorting and tool type apply to task names (for example seo or video editing). Paid placements are skipped. 1 point per returned record.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort. Options: relevance = Relevance (site default), latest = Latest, top-rated = Top rated, most-saved = Most saved, popular = Popular, price = Price, sota = State of the art
keywordYesKeyword or task. e.g. video editing
max_itemsNoMax items (up to 250)
tool_typeNoTool type. Options: apis = APIs, agents = Agents, gpts = GPTs, ios = iOS, mini-tools = Mini tools, android = Android, chrome = Chrome, telegram = Telegram
start_pageNoStarting page

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.0.1

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations provided, the description carries the burden and does disclose real behavioral facts beyond the schema: paid placements are skipped, results cost 1 point per returned record, and sort/tool_type only take effect when the query is a task name. It stops short of describing auth requirements or how start_page interacts with 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 dense sentences, front-loaded with the core action, and no filler. The mid-sentence field list is a little cluttered but serves to tell the agent what comes back in the absence of an output schema.

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 no-output-schema search tool it covers the important ground: what is searched, what is returned, the cost per record, and the paid-placement exclusion. Remaining gaps are modest, mainly pagination/start_page behavior and result-set limits relative to max_items.

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 coverage is 100%, so the baseline is 3, but the description earns above baseline by explaining an interaction the schema cannot express: sort and tool_type apply to task-name queries (e.g. 'seo', 'video editing'). That constraint meaningfully changes how an agent sets those parameters.

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+resource (search AI tools on There's An AI For That) and enumerates the returned fields, which makes the tool's output concrete. It does not, however, distinguish itself from siblings such as run_theresanaiforthat_tools (browse) or run_futurepedia_tools_search, so the agent gets no routing help from the text alone.

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 'by keyword or task name', and the clause that sorting/tool type apply to task names hints at how to shape a query. But there is no explicit when-to-use vs. when-to-use-an-alternative guidance and no mention of the non-search siblings that overlap most closely.

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