Skip to main content
Glama
Sign In

Desearch

by io.github.Desearch-ai
OverviewDiscussionsAdmin

List People Search Tasks

people-search-tasks
Read-only

Your People Search tasks, newest first, with status, counts, cost, why each ended search stopped (completion_reason, coverage_limited), and the metadata labels set on people-search. Free; it lists your own tasks, not the people they found (read those with people-search-status or people-profiles). Use it to find a task_id (filter by metadata to find the searches of one campaign), or to see which searches are still queued, running, or paused: a new search is refused while too many are active.

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": "people-search-tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTasks per page (1-100, API default 20).
cursorNonext_cursor from the previous page. Keep the same metadata filter when you page.
statusNoOnly tasks in these statuses, example: ['running', 'paused'].
metadataNoOnly tasks whose metadata has all of these key/value pairs (exact match, up to 3), example: {"campaign": "q4-outbound"}.
platformNoOnly tasks on this platform: 'x', 'youtube', 'linkedin', or 'tiktok'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"next_cursor from the previous page."New value: +"next_cursor from the previous page. Keep the same metadata filter when you page."
    • addedInput schema / properties / metadata
      Added value: +{
+  "additionalProperties": {
+    "maxLength": 200,
+    "type": "string"
+  },
+  "description": "Only tasks whose metadata has all of these key/value pairs (exact match, up to 3), example: {\"campaign\": \"q4-outbound\"}.",
+  "type": "object"
+}
  2. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, destructiveHint=false), but the description adds traits they cannot express: ordering (newest first), ownership scoping, cost ('Free'), and the throttling consequence that a new search is refused while too many are active. That quota context directly affects how an agent should sequence calls.

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?

Well front-loaded: return contents come first, then scope, then use cases. It is one long run-on sentence chain with parenthetical asides, which is dense but nearly every clause carries information the agent needs.

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?

With no output schema, the description takes on return-value disclosure and does it explicitly by naming the fields returned. Combined with ordering, cost, and the active-task limit, an agent has enough to call this correctly and interpret the result.

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; the description still earns credit by explaining the metadata filter's purpose (finding the searches of one campaign) and tying status to the queued/running/paused states. It does not add anything about limit or cursor beyond the schema, so it stops short of a 5.

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 ('Your People Search tasks, newest first') plus exactly what is returned: status, counts, cost, completion_reason, coverage_limited, and metadata labels. It immediately delimits scope ('lists your own tasks, not the people they found'), which separates it from people-profiles and people-search-status without opening either schema.

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 two concrete jobs ('find a task_id', 'see which searches are still queued, running, or paused') and names the alternatives for the excluded case ('read those with people-search-status or people-profiles'). It even describes the metadata-filter pattern for scoping to one campaign, so the agent knows when this tool is the right entry point.

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

All Desearch toolsInspect
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.

Resources