Creates a private, single-use document-upload request with a 15-minute expiry and 10 MiB file limit. Returns a multipart upload endpoint for direct transfer of file bytes, a request ID, and a browser upload URL as a fallback for files unavailable to the caller. No document is uploaded, order created, payment taken or item sent by this operation.
| 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?
Annotations provide minimal information (all hints false), so the description carries the full burden. It discloses key behaviors: the request is private, single-use, has a 15-minute expiry and a 10 MiB file limit. It also explicitly lists what the operation does NOT do (upload, order, payment, item send), which is valuable for an agent deciding whether to call it. No contradiction with annotations.
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 three concise sentences, front-loaded with the core purpose and constraints, then the return values, and finally the explicit non-actions. Every sentence adds value with no redundancy. It is well-structured and easy to parse.
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 only 2 parameters and no output schema, the description is largely complete: it explains the purpose, behavior, return fields (endpoint, request ID, browser URL), and exclusions. However, it does not explain the parameters, which is a notable omission given the lack of schema descriptions. It also does not explicitly link to the sibling upload tool, though the endpoint hint implies the flow. Overall, it is adequate but could be more complete with parameter explanations.
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?
The schema has 0% description coverage, so the description must compensate. However, the description does not mention either parameter ('service' or 'filename') at all. The enum on 'service' gives some meaning (fax, letter, certified, postcard), but the description does not explain how service affects the request or what filename is for. This is a significant gap; the agent has to guess the role of these parameters.
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 operation: it creates a private, single-use document-upload request with specific constraints (15-minute expiry, 10 MiB limit). It distinguishes itself from the sibling postedly_upload_document by explaining it returns an endpoint for direct transfer, implying this is the preparation step rather than the actual upload. The verb 'creates' and the resource 'document-upload request' are specific and unambiguous.
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 description provides clear context: it is a preparation step that returns an upload endpoint and a browser fallback, and it explicitly states that no document is uploaded, order created, payment taken, or item sent. This implies it should be used before the actual upload, but it does not explicitly name postedly_upload_document as the alternative or state a 'when not to use' condition. The guidance is implicit rather than explicit.
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.