Export synced Velog posts from the local index as Markdown files by username without network requests, making offline backups and archives easier.
Export posts already synced into the local index as Markdown files without making a network request.
| Name | Required | Description | Default |
|---|---|---|---|
| username | Yes |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations exist, so the description carries the full behavioral burden. It usefully discloses the no-network trait, but for a tool that writes files to disk it says nothing about where files land, whether existing files are overwritten, or how errors surface — the details an agent most needs before invoking a filesystem mutation.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single tight sentence with the key scoping constraints (local index, no network) front-loaded. Every clause earns its place and nothing is wasted.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no annotations, no output schema, and zero parameter documentation, the description is too thin for an export tool. An agent cannot determine the destination of the exported Markdown, the meaning of 'username', or whether a prior sync is required before calling it.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the single parameter 'username' is never mentioned in the description. The one input that determines whose posts get exported is left entirely unexplained, with no indication of whether it is a blog identifier, an account name, or what happens with an unknown user.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Export) and resource (posts already synced into the local index) with the output form (Markdown files). The phrase 'already synced into the local index' implicitly separates it from network-facing siblings like velog_list_posts and velog_get_post, though no sibling is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The 'without making a network request' clause implies when this tool is preferable to network-backed siblings, and 'already synced' hints that velog_sync_local_index must run first. However, neither the prerequisite nor the alternative tools are named, so the routing guidance is only implied.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.