Title90/100
Write
The title clearly communicates the tool’s action and subject. Keep it concise.
Description89/100
Drafts an email, message, post, reply, doc, or report in the user's style. Use for new writing for or on behalf of the user, using their current Writing Profile when available. It writes from their request, facts, notes, or an outline, without inventing missing facts. The tool produces the draft. There is no need to draft it first. Works without a Writing Profile. Put the user's directions in `instructions`. It returns finished writing for direct presentation. When presenting the writing, preserve its wording.
The description explains the capability, when to use it, and what to expect.
Inputs76/100
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
profile
The Writing Profile's id or name. To use the current Writing Profile, omit `profile`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
request
What to write: the content, audience, purpose, and facts the user gave. Do not invent facts. Keep writing directions in `instructions`. Describe the intended author and point of view. Required unless `setup` resumes a held request.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
format
The form of the finished writing, such as email, LinkedIn post, Slack message, essay, release notes.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
instructions
The user's directions about tone, length, structure, or exclusions, in their words. If none were given, omit `instructions`. Put content in `request`. Put a named output form in `format`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
language
The language for the finished writing, such as French. When the user requests a language, set `language`. Otherwise, follow the request or source text language.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
requestAuthor
Who wrote the request. `user`: the user. `host`: the assistant. `other`: a third party. If unsure, omit `requestAuthor`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
evidence › source
The source of the user's own material in the current conversation.
Clear enough to supply this argument.
evidence › userApproved
True when the user shared or approved this material for their Writing Profile.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
evidence › writing
Send text the user wrote, unchanged. Remove signatures, quoted replies, forwarded text, boilerplate, prompts, templates, AI text, and any wording you added around their samples.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
evidence › answers › items › question
The question asked.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
evidence › answers › items › answer
The user's answer, unchanged.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
contextHints › source
The source of these preferences in the current conversation.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
contextHints › userApproved
True when the user shared or approved these preferences for this writing task.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
contextHints › preferences
Preferences from the current conversation that matter for this piece. Lasting stated preferences go to `manage_profile`. Preferences together can contain up to 6,000 characters. With `situation.explicitConstraints`, the combined limit is 8,000 characters, including source labels and separators. Exclude secrets and unrelated personal information.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
situation › channel
Known delivery channel, such as email, Slack, document or social post.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
situation › audience
Known reader or audience. If the request does not establish one, omit `audience`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
situation › relationship
Known relationship to the reader, such as teammate, customer, friend or public audience.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
situation › purpose
Known purpose of the writing, such as inform, request, persuade, thank or decline.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
situation › register
The level of formality the user established.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
situation › explicitConstraints
Other constraints the user supplied. Never infer or add constraints here.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
setup › writingJobVersionId
The writing reference returned by the tool.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
setup › purpose
Set `reminder` only to decline the optional reminder after completed writing. Use `choice` `plain`.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
setup › choice
The user's selected option from the returned result.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
setup › templateId
With `choice` `template`, the selected template is required.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
setup › alwaysUse
True when the user asked to use this style for future writing.
Remove validation rules already expressed in this field’s schema; describe its meaning and usage instead.
Annotations100/100
All four behavior hints are declared.
{
"title": "Write",
"readOnlyHint": false,
"openWorldHint": false,
"idempotentHint": false,
"destructiveHint": false
}Output schema0/100
No output schema is declared. Add one for structured results so clients can interpret returned fields.
Not declared