Skip to main content
Glama

jp_lit_export_session

Export your current or historical research sessions as Markdown, JSON, or CSL-JSON for human review or reference management. Preserves full logs, selected candidates, or unselected items.

Instructions

export/write file。現在の調査セッション、または session_id で指定した過去セッションを repo 内の exports/ または output_path に書き出す。既定は Markdown で、人間が読み返しやすい形に整形する。session は読み取るだけで変更しない。cache 一覧や再抽出結果だけを書き出す場合は jp_lit_export_view を使う

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
formatNo出力形式。markdown は人間向け、json は完全な構造化ログ、csl-json は文献管理向け。markdown
profileNo書き出す範囲。full_log は全履歴、selected は選別済み候補、unselected は未選別候補。full_log
overwriteNotrue の場合のみ既存ファイルの上書きを許可する。
session_idNo書き出す過去セッションID。未指定なら現在の調査セッションを書き出す。
output_pathNo出力先ファイルパス。未指定なら repo 内 exports/ に自動生成する。
include_unselectedNomarkdown/json の full_log で未選別候補を含めるかどうか。
allow_external_pathNotrue の場合のみ repo 内 exports/ 外への書き出しを許可する。

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYes
formatYes
profileYes
item_countYes
session_idYes
exported_atYes
Behavior4/5

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

Discloses that the session is read-only (not modified) and output is formatted for human readability. This adds context beyond annotations, which only show readOnlyHint=false (indicating mutation due to file write). The description clarifies that the session data itself is unchanged.

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?

Description is 4 sentences, covering key points without waste. First sentence clearly states the main action. Could be slightly more front-loaded, but still concise.

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

Completeness4/5

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

Given 7 parameters and an output schema, the description provides sufficient context: purpose, default behavior, and a key alternative. Omits details like overwrite permissions or path safety, but those are in schema. A score of 4 reflects good completeness for the complexity.

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 covers all 7 parameters with descriptions (100% coverage). The description only mentions default format and default output path, but does not add significant meaning beyond schema. Baseline score of 3 is appropriate.

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 action (export/write file), the resource (current or past session), the target location (exports/ or output_path), and the default format (Markdown). It distinguishes from the sibling jp_lit_export_view, which is for cache-only export.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

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

Explicitly tells when to use this tool (export full session) and when to use the alternative jp_lit_export_view (for cache list or re-extraction results). No other sibling overlaps, so guidance is clear.

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/itarunnn/jp-lit-mcp'

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