Skip to main content
Glama
Sign In
Search1API MCP Server

Search1API MCP Server

by superagents-lab
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Render the results

render_results
Read-onlyIdempotent

Displays already retrieved results as source cards when UI is supported, or as a readable text list otherwise; does not perform a new search.

Instructions

Present already retrieved source results as source cards when the host supports UI, with a complete readable text list otherwise. Use when the user wants to browse sources or a visual list helps the task. Pass existing results in the desired order; never invent source URLs or factual titles. Does not search, crawl, fetch URLs, verify sources, or consume search credits. Do not call for intermediate research results or when a text answer is sufficient.

Input Schema

NameRequiredDescriptionDefault
titleNoHeading shown above the cards, such as the research topic
resultsYesAlready retrieved results, in the order to display. No new search is performed.

Output Schema

NameRequiredDescriptionDefault
titleYes
totalYesNumber of results in this rendered list, not a provider-wide search total.
resultsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changedv0.9.0
    • changedInput schema / properties / results / items / properties / id / description
      Previous value: -"Copy the original result ID when available. If absent, the server uses its URL."New value: +"The id from the original search result; the server falls back to the URL when there is none"
    • changedInput schema / properties / results / items / properties / metadata / description
      Previous value: -"Optional original JSON source metadata. Do not put credentials or UI implementation details here."New value: +"Metadata from the original result, such as the publication date; never credentials or UI details"
    • changedInput schema / properties / results / items / properties / text / description
      Previous value: -"Optional source snippet or faithful excerpt, not a full page or model-written answer."New value: +"Snippet or faithful excerpt from the source, not a full page or a model-written answer"
    • changedInput schema / properties / results / items / properties / title / description
      Previous value: -"Copy the source title; do not invent or rewrite factual source titles."New value: +"Source title exactly as the search returned it; never invent or rewrite it"
    • changedInput schema / properties / results / items / properties / url / description
      Previous value: -"Absolute HTTP(S) source URL, without embedded credentials."New value: +"Link to the source as the search returned it, never one carrying credentials"
    • changedInput schema / properties / title / description
      Previous value: -"Optional human-readable list heading. Defaults to Results."New value: +"Heading shown above the cards, such as the research topic"
    • changedOutput schema / properties / results / items / properties / id / description
      Previous value: -"Copy the original result ID when available. If absent, the server uses its URL."New value: +"The id from the original search result; the server falls back to the URL when there is none"
    • changedOutput schema / properties / results / items / properties / metadata / description
      Previous value: -"Optional original JSON source metadata. Do not put credentials or UI implementation details here."New value: +"Metadata from the original result, such as the publication date; never credentials or UI details"
    • changedOutput schema / properties / results / items / properties / text / description
      Previous value: -"Optional source snippet or faithful excerpt, not a full page or model-written answer."New value: +"Snippet or faithful excerpt from the source, not a full page or a model-written answer"
    • changedOutput schema / properties / results / items / properties / title / description
      Previous value: -"Copy the source title; do not invent or rewrite factual source titles."New value: +"Source title exactly as the search returned it; never invent or rewrite it"
    • changedOutput schema / properties / results / items / properties / url / description
      Previous value: -"Absolute HTTP(S) source URL, without embedded credentials."New value: +"Link to the source as the search returned it, never one carrying credentials"
  2. Addedv0.8.0

TDQS

A4.8/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses the UI-vs-text fallback that depends on host capability, that no search credits are consumed, that ordering is preserved as passed, and the integrity constraint against inventing URLs or titles. The annotations only cover the read-only/idempotent profile, so this content is genuinely additive.

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?

Front-loaded with the action and its fallback, and every sentence contributes a distinct constraint. The opening sentence is somewhat dense with its host-capability conditional, but nothing is redundant padding.

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

Completeness5/5

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

An output schema exists, so return rendering needn't be explained, and the description covers the remaining risks for this tool type: when to call it, what it must not do, and the integrity constraints on input data. Nothing an agent needs to invoke it correctly is missing.

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 description coverage is 100%, so the schema already documents both parameters and the nested result fields. The description still adds useful semantics by stating results are passed "in the desired order" (order is meaningful, not incidental) and reinforcing the no-fabrication rule for url and title.

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

Purpose5/5

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

States a specific verb and resource ("Present already retrieved source results as source cards") plus the fallback behavior ("complete readable text list otherwise"). This is clearly distinguishable from search/news/crawl siblings, and the tool's role as a pure presentation layer is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit positive triggers ("user wants to browse sources or a visual list helps the task") and explicit negatives ("Do not call for intermediate research results or when a text answer is sufficient"). It also enumerates what it does not do ("Does not search, crawl, fetch URLs, verify sources, or consume search credits"), which routes the agent to the right sibling for those needs.

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