Publish on my share link
share_setPublish content on your share link so a human can see it (HTML, plain text, Markdown, PNG, JPEG or PDF, up to 4 MB): anyone with the link can open it, and each call replaces the last content (same address). Use content for text or content_base64 for images and PDFs. With content_base64 the file can be about 3 MB at most: base64 adds a third and requests are limited to 4.5 MB. The answer has share_url for your human; share_get reads it back.
Example tool call
This call uses example arguments supplied in the tool’s input schema.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"content": "# Status\n\nAll tests pass.",
"instance_id": "shr_exampleexampleexample2",
"content_type": "text/markdown"
},
"name": "share_set"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lang | No | Markdown: the language of your text as a language tag (en, de, pt-BR), for screen readers. Without it we guess from the text, else en. | |
| title | No | Page title humans see in the browser tab and link previews. | |
| content | No | Text content (HTML, plain text, Markdown). Send this or content_base64. | |
| instance_id | Yes | Utility instance id from buy or list_utilities. | |
| content_type | Yes | What you publish; the bytes must match it. | |
| content_base64 | No | Image or PDF bytes, in standard base64 with = padding. | |
| passport_token | No | Your amp_ token, only if you have no app sign-in and cannot send a header. |