Google · Writing From a Brief
Turn approved context into a draft and revise the exact wording you want to keep with Gemini 3.1 Pro.
Compare models for writing and revisions →These are conservative provider estimates and Promptha credits at the stated example settings. Your actual request receives a fresh quote.
Consider it for a brief containing several constraints, such as audience, length and factual details. Separate the writing task from your own fact-checking decision.
The proposed route exposes writing variation and reasoning depth with a bounded output length. The provider’s broader multimodal inputs are not part of this writing adapter.
Compare every name, date and claim with the brief. Structured writing must also pass the existing format validation before it can be saved as a structured result.
Write a two-sentence invitation using only the approved event name, date, time and venue in the selected brief. Use a warm, direct voice. Do not invent admission details.
Illustrative prompt. Select the approved facts when they are needed.
Read the step-by-step guide →Follow the catalog relationships for this model. Compatibility is separate from a tested output.
Open connected model detail →Provider documentation and input schema checked on . Task suggestions are editorial guidance, not a measured comparison. Price estimates are available for registered actions. Workspace activation and live output quality remain separate verification; use the fresh request quote for the actual cost.
Read the Gemini 3.1 Pro provider documentation →Already working in Promptha? Open your workspace to see the models currently enabled for your request.
Gemini 3.1 Pro uses the gemini-3-1-pro action for writing. This action starts from the written request without a required image source. The configured request allows up to 1 output. Exposed structured format choices: json, table, landing_page, vector, design.
Define audience, purpose, length and the facts that must remain accurate. Select only relevant current Knowledge or content records. Make the intended artifact explicit and ask for missing factual details to be omitted rather than invented.
Follow the writing and revisions workflowRead every statement against the approved facts. Check audience, requested length, required wording and unsupported claims before judging style. Keep the selected source draft when asking for a revision so the comparison includes details that were lost as well as improved.
Does the draft satisfy the brief without inventing facts? Keep the source and brief fixed when comparing models. Public model descriptions explain intended uses and input contracts; they are not live benchmarks or evidence of a universal quality ranking.
Compare exact saved versionsThe registered actions documented here do not require a source image. Broader provider multimodal features are separate from the current Promptha controls.
Registered adapters and pricing policy do not guarantee activation. Check enabled models, permissions and current lifecycle in your workspace. An unavailable model needs an explicit compatible replacement and a fresh quote.