Create a report task via the eBay Marketing API to retrieve analytics for specified date ranges, marketplaces, listings, or campaigns, enabling data-driven decisions.
Create report task through the eBay Marketing API.
| Name | Required | Description | Default |
|---|---|---|---|
| request | Yes | Create report task request body |
Changes observed during successful MCP inspections.
v1.14.1Input schema / properties / reportTaskRemoved value: -{
- "additionalProperties": false,
- "description": "Report task configuration",
- "properties": {
- "campaignIds": {
- "description": "Campaign IDs to include in report",
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "dateFrom": {
- "description": "Start date for report data (ISO 8601 format)",
- "type": "string"
- },
- "dateTo": {
- "description": "End date for report data (ISO 8601 format)",
- "type": "string"
- },
- "dimensions": {
- "description": "Report dimensions",
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "marketplaceId": {
- "description": "Marketplace ID",
- "enum": [
- "EBAY_AT",
- "EBAY_AU",
- "EBAY_BE",
- "EBAY_CA",
- "EBAY_CH",
- "EBAY_CN",
- "EBAY_CZ",
- "EBAY_DE",
- "EBAY_DK",
- "EBAY_ES",
- "EBAY_FI",
- "EBAY_FR",
- "EBAY_GB",
- "EBAY_GR",
- "EBAY_HK",
- "EBAY_HU",
- "EBAY_ID",
- "EBAY_IE",
- "EBAY_IL",
- "EBAY_IN",
- "EBAY_IT",
- "EBAY_JP",
- "EBAY_MY",
- "EBAY_NL",
- "EBAY_NO",
- "EBAY_NZ",
- "EBAY_PE",
- "EBAY_PH",
- "EBAY_PL",
- "EBAY_PR",
- "EBAY_PT",
- "EBAY_RU",
- "EBAY_SE",
- "EBAY_SG",
- "EBAY_TH",
- "EBAY_TW",
- "EBAY_US",
- "EBAY_VN",
- "EBAY_ZA",
- "EBAY_HALF_US",
- "EBAY_MOTORS_US"
- ],
- "type": "string"
- },
- "metrics": {
- "description": "Report metrics",
- "items": {
- "type": "string"
- },
- "type": "array"
- },
- "reportType": {
- "description": "Type of report to generate",
- "enum": [
- "CAMPAIGN_PERFORMANCE_REPORT",
- "LISTING_PERFORMANCE_REPORT",
- "KEYWORD_PERFORMANCE_REPORT",
- "ACCOUNT_PERFORMANCE_REPORT"
- ],
- "type": "string"
- }
- },
- "required": [
- "reportType",
- "dateFrom",
- "dateTo"
- ],
- "type": "object"
-}Input schema / properties / requestAdded value: +{
+ "additionalProperties": false,
+ "description": "Create report task request body",
+ "properties": {
+ "campaignIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "channels": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "dateFrom": {
+ "type": "string"
+ },
+ "dateTo": {
+ "type": "string"
+ },
+ "dimensions": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "dimensionKey": {
+ "type": "string"
+ },
+ "dimensionValues": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "fundingModels": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "inventoryReferences": {
+ "items": {
+ "additionalProperties": false,
+ "properties": {
+ "inventoryReferenceId": {
+ "type": "string"
+ },
+ "inventoryReferenceType": {
+ "type": "string"
+ }
+ },
+ "type": "object"
+ },
+ "type": "array"
+ },
+ "listingIds": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "marketplaceId": {
+ "type": "string"
+ },
+ "metricKeys": {
+ "items": {
+ "type": "string"
+ },
+ "type": "array"
+ },
+ "reportFormat": {
+ "type": "string"
+ },
+ "reportType": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "dateFrom",
+ "dateTo",
+ "marketplaceId",
+ "reportType"
+ ],
+ "type": "object"
+}Input schema / requiredPrevious value: -[
- "reportTask"
-]New value: +[
+ "request"
+]v1.8.10Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already state readOnlyHint=false, and the description adds no new behavioral details beyond the act of creation. It doesn't mention that the report task is likely asynchronous, how to monitor its completion, or any side effects.
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?
The description is a single sentence with no redundant words. It front-loads the action and resource, though it omits valuable usage context that could have been added without bloat.
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?
For a tool with a complex nested request schema, no output schema, and minimal annotations, this description is insufficient. It doesn't explain required fields, supported report types, date formats, or how to retrieve the created report task result.
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 100% because the 'request' object has a description, so the baseline is 3. The tool description itself adds no field-level semantics; the many nested fields (reportType, marketplaceId, dateFrom, etc.) remain unexplained.
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?
The description clearly states the verb 'Create' and resource 'report task', scoped to the eBay Marketing API. It distinguishes the tool from get/delete report task siblings by action, though it doesn't explicitly differentiate from other create_* tools.
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?
No guidance is provided on when to use this tool versus alternatives like ebay_get_report_tasks or ebay_delete_report_task. There is no mention of prerequisites, workflow, or conditions that would lead an agent to choose this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.