Skip to main content
Glama

run_research_task

Run a deep web research task that searches, reads, and synthesizes information. Returns a task ID for polling results.

Instructions

Execute a one-time deep web research task. The research agent searches, reads, and synthesizes information from across the web. Returns a task_id for polling. Example: 'latest AI startup funding announcements'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesNatural language description of what to research. Examples: 'What are the latest developments in quantum computing from the past week?', 'Research the competitive landscape for AI code assistants', 'Find pricing information for cloud GPU providers'
user_timezoneNoTimezone for contextual awareness. Example: 'America/New_York'. Default: 'America/Los_Angeles'
user_locationNoLocation for contextual awareness. Format: 'city, region, country'. Default: 'San Francisco, CA, US'
output_fieldsNoOptional: Extract structured data as an array of objects with these field names. Example: ['title', 'summary', 'source_url']. If omitted, returns human-readable text. For complex schemas, call the Yutori REST API directly (see example at: https://docs.yutori.com/reference/research-create#using-webhooks-and-a-structured-output-schema).
webhook_urlNoHTTPS URL to receive webhook notification when research completes. Must use https://.
webhook_formatNoWebhook payload format: 'scout' (default), 'slack', or 'zapier'
Behavior3/5

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

No annotations provided, so description must cover behavior. It discloses async pattern ('returns a task_id for polling'), and describes the agent's actions (searches, reads, synthesizes). However, lacks details on authentication, rate limits, or error handling for the async task. Adequate but not comprehensive.

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?

Efficient at 2 sentences plus examples. Front-loads the purpose. Could be slightly more structured (e.g., bullet points) but overall easy to parse.

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

Completeness3/5

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

Covers the async nature and basic usage. Does not mention related tools like get_research_task_result for polling, which would improve completeness. Given 6 params and no output schema, description is moderately complete but could guide the agent more.

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 each parameter is already described. The description adds minor value with query examples and a note about complex schemas for output_fields. Does not significantly enhance understanding beyond the schema.

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?

Clearly states 'Execute a one-time deep web research task' with specific verb and resource. Examples further clarify scope. Distinguishes from sibling tools like run_browsing_task and create_scout by emphasizing 'deep web research' and 'one-time'.

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 notes one-time nature (vs. scouts for recurring). Provides example queries. Includes a hint about using REST API for complex schemas. Could be more explicit about when not to use (e.g., for single-page browsing) but context from sibling names helps.

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/yutori-ai/yutori-mcp'

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