Skip to main content
Glama

Get Webhound Output

webhound_get_output
Read-onlyIdempotent

Retrieve final reports, working documents, or dataset rows from a Webhound research session by providing the session ID.

Instructions

Read final report/working document or dataset rows. By default this is for terminal sessions only; do not read or summarize partial working notes while a healthy run is still running.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
kindNoauto
selectNooutput
doc_nameNo
session_idYes
allow_partialNoSet true only if the user explicitly asks for an interim/partial update before done=true. Partial output is not final and is not a reason to stop or finalize the run.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
pageNo
rowsNo
toolYes
errorNo
agentsNo
alertsNo
budgetNo
schemaNo
statusNo
blockedNo
datasetNo
healthyNo
messageNo
omittedNo
productNo
resumedNo
showingNo
sourcesNo
stoppedNo
summaryYes
acceptedNo
activityNo
artifactNo
doc_nameNo
doc_typeNo
free_runNo
no_spendNo
requiredNo
documentsNo
is_outputNo
page_sizeNo
retryableNo
truncatedNo
checked_atNo
is_runningNo
message_idNo
new_budgetNo
session_idNo
top_up_urlNo
total_rowsNo
actual_kindNo
api_messageNo
billing_urlNo
document_idNo
next_actionNo
total_linesNo
total_spentNo
amount_addedNo
credit_limitNo
next_actionsNo
output_readyNo
session_typeNo
current_spendNo
error_detailsNo
original_toolNo
selection_keyNo
action_startedNo
budget_controlNo
current_budgetNo
document_stateNo
guidance_addedNo
requested_kindNo
schema_versionYes
complete_outputNo
current_balanceNo
mcp_next_actionNo
previous_budgetNo
session_startedNo
status_snapshotNo
completion_stateNo
content_markdownNo
research_harnessNo
runtime_estimateNo
sidecar_guidanceNo
agent_instructionNo
completion_reasonNo
followup_check_inNo
assembly_triggeredNo
available_documentsNo
forbidden_next_toolsNo
auto_recharge_enabledNo
successful_completionNo
user_message_templateNo
evidence_pack_instructionNo
next_research_instructionNo
retry_after_user_confirmsNo
output_deferred_until_doneNo
Behavior4/5

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

The description goes beyond the annotations (readOnlyHint=true, idempotentHint=true) by warning against reading partial working notes during an active run, which is a key behavioral constraint. It does not contradict any annotations. While it lacks details on rate limits or authentication, the annotation set already covers the safety profile, and the warning adds valuable context.

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 two sentences long, front-loaded with the purpose, and includes only essential information. Every sentence serves a clear function: stating the tool's action and providing a critical usage constraint. No unnecessary words or repetition.

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 5 parameters and a low schema coverage (20%), the description is minimal and does not explain multiple parameter options or their interplay. It lacks details about the 'kind' and 'select' enums, and while an output schema exists, the description does not hint at what the output contains. The warning about partial runs is useful, but overall the description is incomplete for this tool's complexity.

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?

The input schema has 5 parameters with only 20% description coverage (only allow_partial has a description). The description does not explain the meaning of 'kind' (auto/report/dataset) or 'select' (output/working/latest) parameters, nor does it clarify the role of doc_name. Given the low schema coverage, the description should compensate, but it does not, leaving the agent to guess parameter semantics.

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 reads final reports, working documents, or dataset rows. It distinguishes itself from sibling tools by specifying 'terminal sessions only' and by focusing on reading output rather than other operations. However, the phrase 'terminal sessions' could be more explicit, and it doesn't fully differentiate from other read tools like get_session or get_evidence_pack.

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?

The description provides a clear when-not-to-use: do not read partial working notes while a healthy run is running. However, it does not explicitly mention when to use this tool over alternative sibling tools, such as webhound_get_session or webhound_get_evidence_pack. The guidance is present but incomplete.

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