EvenLeads

Find hiring requests

find_hiring_requests

Read-onlyIdempotent

Search recent public posts where someone asks to hire a freelancer or agency for a service (web design, development, Shopify, WordPress, SEO, ads, video, copywriting, design, social media, virtual assistants and more). Returns the niche, request type, budget if stated, platform, community and age; post links are included after the user signs in with EvenLeads. Covers freelance and agency services only; works without signing in.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "find_hiring_requests"
  }
}

Input Schema

Name	Required	Description
`hours`	No	How far back to look in hours (1-168). Default 48.
`limit`	No	Number of results (1-10). Default 5.
`niche`	No	Optional niche slug, as listed by the niche list.
`query`	No	The service in plain words, e.g. "shopify developer", "logo design", "seo for dentists".

Output Schema

Name	Required	Description	Default
`total`	No
`niches`	No
`results`	No
`links_included`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 15, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely new behavior: post links are gated behind an EvenLeads sign-in, the tool still returns results without auth, and results carry niche, request type, budget, platform, community and age. It stops short of noting result caps or rate limits.

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, front-loaded with the core purpose and followed by return fields and constraints. The parenthetical service list ('web design, development, Shopify, WordPress, SEO, ads...') is somewhat long but does usefully bound the domain; little else is wasted.

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?

The tool has four optional parameters, full schema descriptions and an output schema, so the return-shape burden is light. The description covers scope, auth gating and content of results, leaving only minor gaps such as result limits and whether unauthenticated results are truncated.

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%, so hours, limit, niche and query are already fully documented in the schema. The description only echoes the concepts ('recent', 'niche', 'budget if stated') without adding format, defaults or interaction semantics, so the baseline of 3 applies.

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 and resource: 'Search recent public posts where someone asks to hire a freelancer or agency for a service', and narrows the domain to freelance/agency service requests. This is clearly different from a generic 'search' or 'find_customers', though it never names those siblings directly, so the differentiation is inferred rather than stated.

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?

'Covers freelance and agency services only' implies a negative case (don't use it for non-service or non-freelance queries), and 'works without signing in' hints at a low-friction context. There is no explicit when-to-use versus an alternative tool, and no guidance on when to prefer this over search or find_customers.

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

All EvenLeads tools Inspect

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.