Creates a private, single-use document-upload request with a 15-minute expiry and a 10 MiB file limit. Returns a request ID, a multipart upload endpoint for direct transfer of the file bytes, and a browser upload URL where a person can upload the file instead. Does not upload a document, create a quote or order, take payment or send anything.
| Name | Required | Description | Default |
|---|---|---|---|
| service | Yes | ||
| filename | No |
Changes observed during successful MCP inspections.
Output schema / (root)Previous value: -{
- "$schema": "https://json-schema.org/draft/2020-12/schema",
- "anyOf": [
- {
- "additionalProperties": false,
- "properties": {
- "documentRequestId": {
- "minLength": 1,
- "type": "string"
- },
- "expiresAt": {
- "type": "string"
- },
- "instructions": {
- "type": "string"
- },
- "maxFileBytes": {
- "const": 10485760
- },
- "uploadEncoding": {
- "const": "multipart/form-data"
- },
- "uploadEndpoint": {
- "format": "uri",
- "type": "string"
- },
- "uploadField": {
- "const": "file"
- },
- "uploadMethod": {
- "const": "POST"
- },
- "uploadUrl": {
- "format": "uri",
- "type": "string"
- }
- },
- "required": [
- "documentRequestId",
- "uploadUrl",
- "expiresAt",
- "uploadEndpoint",
- "uploadMethod",
- "uploadEncoding",
- "uploadField",
- "maxFileBytes",
- "instructions"
- ],
- "type": "object"
- },
- {
- "additionalProperties": false,
- "properties": {
- "error": {
- "additionalProperties": false,
- "properties": {
- "code": {
- "minLength": 1,
- "type": "string"
- },
- "details": {
- "additionalProperties": false,
- "properties": {
- "addressRole": {
- "enum": [
- "recipient",
- "sender"
- ]
- },
- "canSendAsEntered": {
- "type": "boolean"
- }
- },
- "required": [
- "addressRole",
- "canSendAsEntered"
- ],
- "type": "object"
- },
- "message": {
- "type": "string"
- }
- },
- "required": [
- "code",
- "message"
- ],
- "type": "object"
- }
- },
- "required": [
- "error"
- ],
- "type": "object"
- }
- ],
- "type": "object"
-}New value: +nullOutput schema / (root)Previous value: -nullNew value: +{
+ "$schema": "https://json-schema.org/draft/2020-12/schema",
+ "anyOf": [
+ {
+ "additionalProperties": false,
+ "properties": {
+ "documentRequestId": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "expiresAt": {
+ "type": "string"
+ },
+ "instructions": {
+ "type": "string"
+ },
+ "maxFileBytes": {
+ "const": 10485760
+ },
+ "uploadEncoding": {
+ "const": "multipart/form-data"
+ },
+ "uploadEndpoint": {
+ "format": "uri",
+ "type": "string"
+ },
+ "uploadField": {
+ "const": "file"
+ },
+ "uploadMethod": {
+ "const": "POST"
+ },
+ "uploadUrl": {
+ "format": "uri",
+ "type": "string"
+ }
+ },
+ "required": [
+ "documentRequestId",
+ "uploadUrl",
+ "expiresAt",
+ "uploadEndpoint",
+ "uploadMethod",
+ "uploadEncoding",
+ "uploadField",
+ "maxFileBytes",
+ "instructions"
+ ],
+ "type": "object"
+ },
+ {
+ "additionalProperties": false,
+ "properties": {
+ "error": {
+ "additionalProperties": false,
+ "properties": {
+ "code": {
+ "minLength": 1,
+ "type": "string"
+ },
+ "details": {
+ "additionalProperties": false,
+ "properties": {
+ "addressRole": {
+ "enum": [
+ "recipient",
+ "sender"
+ ]
+ },
+ "canSendAsEntered": {
+ "type": "boolean"
+ }
+ },
+ "required": [
+ "addressRole",
+ "canSendAsEntered"
+ ],
+ "type": "object"
+ },
+ "message": {
+ "type": "string"
+ }
+ },
+ "required": [
+ "code",
+ "message"
+ ],
+ "type": "object"
+ }
+ },
+ "required": [
+ "error"
+ ],
+ "type": "object"
+ }
+ ],
+ "type": "object"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Goes well beyond annotations by disclosing privacy (private), single-use semantics, a 15-minute expiry, a 10 MiB file limit, and the three returned artifacts (request ID, multipart endpoint, browser URL). The annotations only cover safety hints; the description supplies the operational constraints an agent needs.
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?
Three tightly packed sentences with no filler; the core action and constraints are front-loaded and the exclusions close the definition.
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 output schema, the description correctly documents the return values (request ID, upload endpoints) and the lifetime/size constraints. Nothing essential to correct invocation is missing aside from parameter documentation.
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 coverage is 0% for two parameters (service enum and filename), and the description never mentions either parameter or explains the fax/letter/certified/postcard values. The 10 MiB mention concerns the file, not the filename argument, so the description does not compensate for the coverage gap.
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 and resource ('Creates a private, single-use document-upload request') with concrete scope (15-minute expiry, 10 MiB limit). It clearly distinguishes itself from siblings like postedly_upload_document and postedly_checkout by declaring what it does not do.
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 closing sentence provides explicit when-not guidance ('Does not upload a document, create a quote or order, take payment or send anything'), which routes the agent away from postedly_upload_document and postedly_checkout. However, it never names those alternatives explicitly or states the positive condition for choosing this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.