Prompts changedspecification/draft/server/prompts
Nearest release: v2.1.305, published under an hour before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 20 Oct 2026 20:02 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 22 Oct 2026 20:37 UTC.
Upstream edited
Recorded here
Lines+6added
Lines−6removed
From line
64
where the diff opens
First seen
26 Aug 2026
this site's first read of the page
Recorded edits3to this page, all time
The whole hunk
from line 64, old and new numbered
/
from line 64
6464### Listing Prompts
6565
6666To retrieve available prompts, clients send a `prompts/list` request. This operation
67supports [pagination](/specification/draft/server/utilities/pagination) and [caching](/specification/draft/server/utilities/caching).
67supports [pagination](/specification/draft/server/utilities/pagination.md) and [caching](/specification/draft/server/utilities/caching.md).
6868
6969**Request:**
7070
from line 118
118118### Getting a Prompt
119119
120120To retrieve a specific prompt, clients send a `prompts/get` request. Arguments may be
121auto-completed through [the completion API](/specification/draft/server/utilities/completion).
121auto-completed through [the completion API](/specification/draft/server/utilities/completion.md).
122122
123123**Request:**
124124
from line 158
158158}
159159```
160160
161Servers **MAY** also respond to `prompts/get` with an [`InputRequiredResult`](/specification/draft/basic/patterns/mrtr#inputrequiredresult) to indicate that additional input is needed before the prompt can be resolved. This follows the [multi round-trip requests](/specification/draft/basic/patterns/mrtr#multi-round-trip-requests) mechanism. When retrying the request, clients include `inputResponses` and, if provided by the server, `requestState` in the request parameters.
161Servers **MAY** also respond to `prompts/get` with an [`InputRequiredResult`](/specification/draft/basic/patterns/mrtr#inputrequiredresult) to indicate that additional input is needed before the prompt can be resolved. This follows the [multi round-trip requests](/specification/draft/basic/patterns/mrtr.md#multi-round-trip-requests) mechanism. When retrying the request, clients include `inputResponses` and, if provided by the server, `requestState` in the request parameters.
162162
163163### List Changed Notification
164164
from line 221
221221> [!NOTE]
222222>
223223> All content types in prompt messages support optional
224> [annotations](/specification/draft/server/resources#annotations) for metadata
224> [annotations](/specification/draft/server/resources.md#annotations) for metadata
225225> about audience, priority, and modification times.
226226
227227#### Text Content
from line 270
270270#### Resource Links
271271
272272Prompt messages **MAY** include links to
273[Resources](/specification/draft/server/resources), to provide additional context or
273[Resources](/specification/draft/server/resources.md), to provide additional context or
274274data without embedding the resource contents directly. In this case, the prompt message
275275returns a URI that can be fetched by the client:
276276
from line 284
284284}
285285```
286286
287Resource links support the same [Resource annotations](/specification/draft/server/resources#annotations)
287Resource links support the same [Resource annotations](/specification/draft/server/resources.md#annotations)
288288as regular resources to help clients understand how to use them.
289289
290290#### Embedded Resources
No line in this hunk matches that.