Skip to main content
Glama
KyuRish

trading212-mcp-server

by KyuRish
OverviewSchemaRelated ServersScoreDiscussions(1)
Python

request_csv_export

Queue an asynchronous CSV export of Trading 212 account history, including dividends, interest, orders, and transactions. Specify optional time range to limit data. Track progress and get download link via fetch_exports_list.

Instructions

Queue a CSV export of your account history. The export runs asynchronously -
check fetch_exports_list to monitor progress and get the download link.

This creates a server-side export job. Each call generates a new report.
Use the time range parameters to limit the export to a specific period.

Args:
    include_dividends: Include dividend payment records. Defaults to True.
    include_interest: Include interest payment records. Defaults to True.
    include_orders: Include trade/order history. Defaults to True.
    include_transactions: Include deposit/withdrawal records. Defaults to True.
    time_from: Start of the reporting window in ISO 8601 (e.g., '2024-01-01T00:00:00Z').
        Omit for all history.
    time_to: End of the reporting window in ISO 8601 (e.g., '2024-12-31T23:59:59Z').
        Omit for up to now.

Returns:
    EnqueuedReport with the reportId for tracking via fetch_exports_list

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
include_dividendsNo
include_interestNo
include_ordersNo
include_transactionsNo
time_fromNo
time_toNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportIdYes

Tool Definition Quality

A4.7/5.0
Behavior5/5

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

Annotations indicate non-read-only, non-destructive, non-idempotent. The description adds key behaviors: runs asynchronously, each call generates a new report, and returns an EnqueuedReport with reportId. No contradictions.

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?

The description is well-structured with a brief intro, async behavior note, and a docstring-style Args/Returns. Every sentence is informative, though slightly lengthy. Could be tightened but still effective.

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

Completeness5/5

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

Given the tool's complexity (6 parameters, async, sibling tool), the description covers purpose, async handling, parameter details, return value, and how to track progress. No gaps identified.

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

Parameters5/5

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

Schema description coverage is 0%, but the description provides detailed explanations for all 6 parameters via an Args section, including defaults, format for time parameters, and meaning of omission. This greatly adds value beyond the schema.

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 tool queues a CSV export of account history, with a specific verb 'queue' and resource 'CSV export'. It distinguishes itself from sibling fetch_exports_list by noting the export runs asynchronously and that sibling is used for monitoring.

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 explicitly guides when to use this tool (to start an export) and points to fetch_exports_list for progress and download. It notes each call creates a new report, implying non-idempotency, but doesn't explicitly state when not to use it.

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/KyuRish/trading212-mcp-server'

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