Skip to main content
Glama

Export Webhound Session

webhound_export_session
Read-onlyIdempotent

Export completed reports or datasets as Markdown, HTML, TXT, JSON, CSV, JSONL, or PDF. Use after investigation finishes to retrieve structured output without spending credits.

Instructions

Export a completed report or dataset as Markdown, HTML, TXT, JSON traces, CSV, JSONL, or PDF. Does not spend credits. Wait for done=true before exporting unless the user explicitly asks for a partial artifact.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNoauto
selectNooutput
doc_nameNo
session_idYes
allow_partialNoSet true only if the user explicitly asks for an interim/partial export before done=true.
include_contentNo
include_binary_base64NoBinary exports default to a download URL because base64 is not useful agent context. Set true only when raw binary bytes are required in the MCP response.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
okYes
urlNo
bodyNo
codeNo
costNo
dataNo
doneNo
kindNo
nameNo
toolYes
errorNo
agentsNo
alertsNo
budgetNo
formatNo
statusNo
blockedNo
contentNo
datasetNo
healthyNo
messageNo
omittedNo
productNo
resumedNo
stoppedNo
summaryYes
acceptedNo
activityNo
deliveryNo
encodingNo
filenameNo
free_runNo
no_spendNo
requiredNo
documentsNo
mime_typeNo
retryableNo
row_countNo
checked_atNo
is_runningNo
message_idNo
new_budgetNo
session_idNo
size_bytesNo
top_up_urlNo
api_messageNo
billing_urlNo
next_actionNo
total_spentNo
amount_addedNo
credit_limitNo
download_urlNo
next_actionsNo
output_readyNo
session_typeNo
current_spendNo
download_noteNo
error_detailsNo
original_toolNo
action_startedNo
budget_controlNo
content_base64No
current_budgetNo
document_countNo
guidance_addedNo
schema_versionYes
complete_exportNo
current_balanceNo
mcp_next_actionNo
previous_budgetNo
session_startedNo
status_snapshotNo
completion_stateNo
research_harnessNo
runtime_estimateNo
sidecar_guidanceNo
agent_instructionNo
completion_reasonNo
content_truncatedNo
followup_check_inNo
supported_formatsNo
assembly_triggeredNo
binary_download_urlNo
forbidden_next_toolsNo
auto_recharge_enabledNo
successful_completionNo
user_message_templateNo
evidence_pack_instructionNo
next_research_instructionNo
retry_after_user_confirmsNo
export_deferred_until_doneNo
Behavior4/5

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds that credits are not consumed and that waiting for done=true is required. No contradictions with 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?

Two sentences, no filler. First sentence delivers the core action and outputs. Second sentence adds crucial behavioral guidance. Every word serves a purpose.

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?

Given 7 parameters, low schema coverage, and many siblings, the description covers the main action and a key constraint. However, it lacks details on parameter options and does not differentiate from similar export/retrieve siblings beyond listing formats.

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 low (29%). Description does not explain most parameters (format, select, doc_name, include_content, include_binary_base64) beyond implicit mentions. Only hints at allow_partial via the 'wait for done' rule.

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 'export' and specifies the resource as a completed report or dataset. It lists exact output formats (Markdown, HTML, TXT, JSON traces, CSV, JSONL, PDF), which distinguishes it from sibling tools like webhound_get_output or webhound_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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit conditions: wait for done=true unless user requests partial. Also states 'Does not spend credits,' giving cost context. However, no direct comparison with alternative sibling tools for similar tasks.

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