Skip to main content
Glama

Search Public APIs

search_public_apis
Read-onlyIdempotent

Searches a curated catalog of 600+ free public APIs (no key, HTTPS) for embedding live data in display HTML via fetch(): weather, news, finance, sports, images, food and 40+ more categories. Use when generating HTML that needs live internet data. Set list_categories=true to get the category menu with counts instead of search results. Returns docs links, CORS status and fetch() hints. No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum results, 1-20. Default 10.
queryNoFree-text search, e.g. 'weather forecast', 'bitcoin price', 'jokes'.
categoryNoCategory ID filter, e.g. 'weather', 'finance', 'news'. Omit for all.
cors_onlyNotrue returns only APIs with confirmed browser CORS support. Default false.
list_categoriesNotrue returns all categories with API counts instead of search results.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countNo
queryNo
resultsNo
categoryNo
corsOnlyNo
categoriesNo
totalCatalogApisNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Filter by category ID. Examples: 'weather', 'finance', 'animals', 'food-drink', 'sports-fitness', 'news', 'entertainment'. Use 'all' or omit for all categories."New value: +"Category ID filter, e.g. 'weather', 'finance', 'news'. Omit for all."
    • changedInput schema / properties / cors_only / description
      Previous value: -"When true, only return APIs with confirmed CORS support (safe for browser-side fetch in HTML). Defaults to false."New value: +"true returns only APIs with confirmed browser CORS support. Default false."
    • changedInput schema / properties / limit / description
      Previous value: -"Maximum results to return, 1-20. Defaults to 10."New value: +"Maximum results, 1-20. Default 10."
    • addedInput schema / properties / list_categories
      Added value: +{
      +  "description": "true returns all categories with API counts instead of search results.",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Free-text search terms. Examples: 'weather forecast', 'random quotes', 'cat pictures', 'bitcoin price', 'jokes'."New value: +"Free-text search, e.g. 'weather forecast', 'bitcoin price', 'jokes'."
    • addedOutput schema / properties / categories
      Added value: +{
      +  "items": {
      +    "properties": {
      +      "count": {
      +        "type": [
      +          "integer",
      +          "null"
      +        ]
      +      },
      +      "id": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      },
      +      "name": {
      +        "type": [
      +          "string",
      +          "null"
      +        ]
      +      }
      +    },
      +    "type": [
      +      "object",
      +      "null"
      +    ]
      +  },
      +  "type": [
      +    "array",
      +    "null"
      +  ]
      +}
  2. Changed15 schema fields changed
    • changedOutput schema / properties / category / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / corsOnly / type
      Previous value: -"boolean"New value: +[
      +  "boolean",
      +  "null"
      +]
    • changedOutput schema / properties / count / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "null"
      +]
    • changedOutput schema / properties / query / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / category / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / cors / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / description / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / fetchUri / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / htmlEmbeddingHint / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / link / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / name / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / properties / slug / type
      Previous value: -"string"New value: +[
      +  "string",
      +  "null"
      +]
    • changedOutput schema / properties / results / items / type
      Previous value: -"object"New value: +[
      +  "object",
      +  "null"
      +]
    • changedOutput schema / properties / results / type
      Previous value: -"array"New value: +[
      +  "array",
      +  "null"
      +]
    • changedOutput schema / properties / totalCatalogApis / type
      Previous value: -"integer"New value: +[
      +  "integer",
      +  "null"
      +]
  3. Changed13 schema fields changed
    • removedInput schema / properties / category / default
      Removed value: -null
    • changedInput schema / properties / category / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • removedInput schema / properties / corsOk
      Removed value: -{
      -  "default": null,
      -  "description": "When true, return only APIs verified by agentView's nightly CORS probe to be usable from a browser display. Synonym of cors_only. Defaults to false.",
      -  "type": [
      -    "boolean",
      -    "null"
      -  ]
      -}
    • removedInput schema / properties / cors_only / default
      Removed value: -null
    • changedInput schema / properties / cors_only / description
      Previous value: -"When true, return only APIs verified by agentView's nightly CORS probe to be usable from a browser display (corsOk AND reachable). Alias for corsOk. Defaults to false."New value: +"When true, only return APIs with confirmed CORS support (safe for browser-side fetch in HTML). Defaults to false."
    • changedInput schema / properties / cors_only / type
      Previous value: -[
      -  "boolean",
      -  "null"
      -]New value: +"boolean"
    • removedInput schema / properties / limit / default
      Removed value: -null
    • addedInput schema / properties / limit / maximum
      Added value: +20
    • addedInput schema / properties / limit / minimum
      Added value: +1
    • changedInput schema / properties / limit / type
      Previous value: -[
      -  "integer",
      -  "null"
      -]New value: +"integer"
    • removedInput schema / properties / query / default
      Removed value: -null
    • changedInput schema / properties / query / type
      Previous value: -[
      -  "string",
      -  "null"
      -]New value: +"string"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "category": {
      +      "type": "string"
      +    },
      +    "corsOnly": {
      +      "type": "boolean"
      +    },
      +    "count": {
      +      "type": "integer"
      +    },
      +    "query": {
      +      "type": "string"
      +    },
      +    "results": {
      +      "items": {
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "cors": {
      +            "type": "string"
      +          },
      +          "description": {
      +            "type": "string"
      +          },
      +          "fetchUri": {
      +            "type": "string"
      +          },
      +          "htmlEmbeddingHint": {
      +            "type": "string"
      +          },
      +          "link": {
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "slug": {
      +            "type": "string"
      +          }
      +        },
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "totalCatalogApis": {
      +      "type": "integer"
      +    }
      +  },
      +  "type": "object"
      +}
  4. Changed2 schema fields changed
    • addedInput schema / properties / corsOk
      Added value: +{
      +  "default": null,
      +  "description": "When true, return only APIs verified by agentView's nightly CORS probe to be usable from a browser display. Synonym of cors_only. Defaults to false.",
      +  "type": [
      +    "boolean",
      +    "null"
      +  ]
      +}
    • changedInput schema / properties / cors_only / description
      Previous value: -"When true, only return APIs with confirmed CORS support (safe for browser-side fetch in HTML). Defaults to false."New value: +"When true, return only APIs verified by agentView's nightly CORS probe to be usable from a browser display (corsOk AND reachable). Alias for corsOk. Defaults to false."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Discloses no authentication required, returns docs links, CORS status, and fetch() hints. Annotations already declare readOnlyHint and idempotentHint, and the description adds context about the curated catalog size and category count.

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 sentences, well front-loaded with purpose and usage. Second sentence is slightly long but packs important details. No wasted words.

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?

Given 5 parameters and output schema present, the description covers key use cases, parameter behavior, and return details. No gaps identified.

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 baseline 3. Description adds value by explaining list_categories behavior beyond schema (returns category menu with counts), and gives query examples like 'weather forecast'.

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?

Description clearly states it searches a curated catalog of free public APIs, specifying the use case for embedding live data in HTML via fetch(). It distinguishes from sibling tools like search or search_store_templates by focusing on public APIs with no auth required.

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

Usage Guidelines4/5

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

Explicitly says 'Use when generating HTML that needs live internet data' and describes the list_categories option for category navigation. Does not mention alternatives, but context signals and sibling list provide differentiation.

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.

Resources