Skip to main content
Glama

Start Webhound Dataset

webhound_start_dataset

Start a private dataset extraction for research. Adjust budget to control depth and monitor until completion.

Instructions

Start a private long-running dataset with Hound, Webhound's DeepSeek V4 Pro + GPT-5.4 research harness. Budget controls extraction depth; watch until done=true. Do not force finalization before done=true.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNo
budgetNo
promptYes
schemaNoOptional explicit schema. Native example: {"entity_name":"Company","attributes":[{"name":"company_name","type":"string","is_primary":true,"description":"Official company name"},{"name":"website","type":"string","standard_format":"url"},{"name":"employee_count","type":"number"}]} JSON Schema example: {"type":"object","title":"Company","required":["company_name"],"properties":{"company_name":{"type":"string","description":"Official company name","x-webhound-primary":true},"website":{"type":"string","format":"uri"},"employee_count":{"type":"integer"}}}
file_idsNo
enable_checkpointsNo
context_session_idsNo
use_free_run_when_availableNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
toolYes
errorNo
agentsNo
alertsNo
budgetNo
statusNo
blockedNo
datasetNo
healthyNo
messageNo
productNo
resumedNo
stoppedNo
summaryYes
acceptedNo
activityNo
free_runNo
no_spendNo
requiredNo
documentsNo
retryableNo
checked_atNo
is_runningNo
message_idNo
new_budgetNo
session_idNo
top_up_urlNo
api_messageNo
billing_urlNo
next_actionNo
total_spentNo
amount_addedNo
credit_limitNo
next_actionsNo
output_readyNo
session_typeNo
current_spendNo
error_detailsNo
original_toolNo
schema_sourceNo
action_startedNo
budget_controlNo
current_budgetNo
guidance_addedNo
schema_versionYes
current_balanceNo
mcp_next_actionNo
previous_budgetNo
schema_warningsNo
session_startedNo
status_snapshotNo
completion_stateNo
research_harnessNo
runtime_estimateNo
sidecar_guidanceNo
agent_instructionNo
completion_reasonNo
followup_check_inNo
normalized_schemaNo
assembly_triggeredNo
schema_input_formatNo
forbidden_next_toolsNo
auto_recharge_enabledNo
successful_completionNo
user_message_templateNo
retry_after_user_confirmsNo
Behavior4/5

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

Annotations indicate openWorldHint=true, but description adds context about the tool being asynchronous and long-running. It warns against premature finalization. No contradictions. However, it does not elaborate on side effects or non-idempotent behavior beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise—two sentences—with the main action first and usage notes second. No extraneous words, effectively front-loaded.

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?

Despite having an output schema, the description does not explain return values or the complex 'schema' parameter. For a tool with 8 parameters and asynchronous behavior, the description is too brief to be complete. An AI agent would lack critical details for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 13%, and the description barely explains any parameters. Only 'budget' is mentioned ('controls extraction depth'). Other critical parameters like 'prompt', 'schema', 'file_ids' etc. are not described, leaving the agent without sufficient guidance.

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?

The description clearly states the verb 'start' and the resource 'private long-running dataset' with specific technology details (DeepSeek V4 Pro + GPT-5.4 research harness). It distinguishes from sibling tools like webhound_start_report, which is for reports.

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?

The description provides guidance on usage: 'Budget controls extraction depth; watch until done=true. Do not force finalization before done=true.' It implicitly suggests using webhound_watch after starting. However, it does not explicitly state when not to use this tool or compare directly to alternatives.

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/WebhoundAI/webhound-mcp'

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