Skip to main content
Glama

find_similar

Find web pages similar to a given URL. Refine results with filters for date range, domain, and content category.

Instructions

Find pages similar to a given URL using Exa.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesThe URL to find similar pages for.
num_resultsNoNumber of results to return.
contentsNoOptions for retrieving page contents. Use False to disable.
include_domainsNoDomains to include in the search.
exclude_domainsNoDomains to exclude from the search.
start_crawl_dateNoOnly links crawled after this date (YYYY-MM-DD).
end_crawl_dateNoOnly links crawled before this date (YYYY-MM-DD).
start_published_dateNoOnly links published after this date (YYYY-MM-DD).
end_published_dateNoOnly links published before this date (YYYY-MM-DD).
include_textNoStrings that must appear in the page text.
exclude_textNoStrings that must not appear in the page text.
exclude_source_domainNoWhether to exclude the source domain.
categoryNoData category to focus on.
flagsNoExperimental flags for Exa usage.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior2/5

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

No annotations are provided, and the description does not mention any behavioral traits such as rate limits, data consumption, or whether results are cached. The tool performs a network operation, but this is not disclosed.

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?

The description is a single sentence without fluff, but it may be too terse for the complexity of the tool. It is front-loaded and efficient.

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?

Given the tool has 14 parameters and an output schema, the description is too brief to provide sufficient context. More information about typical usage or result format would be beneficial.

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?

The input schema has 100% description coverage, so the schema already documents all parameters. The description adds no additional meaning beyond 'using Exa'. Baseline 3 is appropriate.

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 clearly states the tool finds pages similar to a given URL using Exa, with a specific verb and resource. However, it does not elaborate on the similarity algorithm or distinguish from related tools like search.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus siblings like search, get_contents, or answer. The description lacks context on prerequisites or typical use cases.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/daedalus/mcp-exa'

If you have feedback or need assistance with the MCP directory API, please join our Discord server