Skip to main content
Glama
YosefHayim

ebay-mcp

by YosefHayim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

ebay_create_vero_report

Report intellectual property infringement on eBay listings through the VeRO Program. Submit a VERO report to flag listings that violate your rights.

Instructions

Create a VERO report to report intellectual property infringement. This endpoint is part of the Verified Rights Owner (VeRO) Program and allows rights owners to report listings that infringe on their intellectual property.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
reportDataYesGenerated VeroReportItemsRequest body

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.14.1
    • changedInput schema / properties / reportData / additionalProperties
      Previous value: -trueNew value: +false
    • changedInput schema / properties / reportData / description
      Previous value: -"VERO report data containing item details and intellectual property violation information"New value: +"Generated VeroReportItemsRequest body"
    • removedInput schema / properties / reportData / properties / items
      Removed value: -{
-  "items": {
-    "additionalProperties": false,
-    "properties": {
-      "itemId": {
-        "type": "string"
-      },
-      "reportingReason": {
-        "type": "string"
-      }
-    },
-    "required": [
-      "itemId",
-      "reportingReason"
-    ],
-    "type": "object"
-  },
-  "type": "array"
-}
    • removedInput schema / properties / reportData / properties / message
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / reportData / properties / reportItems
      Added value: +{
+  "items": {
+    "additionalProperties": false,
+    "properties": {
+      "brand": {
+        "type": "string"
+      },
+      "copyEmailToRightsOwner": {
+        "type": "boolean"
+      },
+      "countries": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "detailedMessage": {
+        "type": "string"
+      },
+      "itemId": {
+        "type": "string"
+      },
+      "messageToSeller": {
+        "type": "string"
+      },
+      "patent": {
+        "type": "string"
+      },
+      "regions": {
+        "items": {
+          "type": "string"
+        },
+        "type": "array"
+      },
+      "veroReasonCodeId": {
+        "type": "string"
+      }
+    },
+    "type": "object"
+  },
+  "type": "array"
+}
    • removedInput schema / properties / reportData / properties / rightsOwnerEmail
      Removed value: -{
-  "format": "email",
-  "type": "string"
-}
    • removedInput schema / properties / reportData / required
      Removed value: -[
-  "items"
-]
  2. First observedv1.8.10

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description must fully disclose behavior. It does not mention consequences, reversibility, permissions, rate limits, or any side effects of creating a report.

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?

The description is two concise sentences, front-loaded with the core action. Every sentence adds value with no redundant or extraneous content.

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

Completeness2/5

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

Despite a single parameter, the nested object is complex. The description lacks information about response format, prerequisites (e.g., VeRO membership), error handling, or any process beyond creation. Without annotations, the description is insufficient for an agent to confidently use the tool.

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?

The tool description adds no information about the parameters beyond what is in the schema. The schema description for 'reportData' is generic ('Generated VeroReportItemsRequest body'), and nested properties lack descriptions. The tool description does not compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a VERO report for intellectual property infringement, with specific verb 'create' and resource 'VERO report'. However, it does not explicitly differentiate from sibling tools like ebay_get_vero_report, though the creation purpose is clear.

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

Usage Guidelines3/5

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

The description implies usage by rights owners in the VeRO Program, but lacks explicit guidance on when to use this tool versus alternatives, or any exclusions or prerequisites.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools