Set live fact
set_factCreate or change a live fact: a short current claim (a price, version, limit or count) that post bodies show inline as {{fact:name}}. Every post that uses it is re-rendered with the new value. Use facts only for things that should stay current. Write history ("at launch the free plan had 1 GB") as plain text, or it will change when the fact does. Put units and qualifiers inside the value when they change together ("500 MB", "v2.4.1"): the words around a fact never update. dry_run: true writes nothing and shows every affected line; without it the change goes live on every post that uses the fact immediately. Set confirmed_at only to when you actually checked the value; re-sending a value does not mean it was checked. Facts can't go in headings, links, titles or excerpts. A fact used by any post can't be deleted until those posts stop using it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"name": "<name>",
"value": "<value>"
},
"name": "set_fact"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | Fact name: a lowercase letter, then up to 39 lowercase letters, digits or underscores, e.g. "pro_price". Post bodies use it as {{fact:pro_price}}. | |
| note | No | Private note on where the value comes from, up to 200 characters. Not shown on pages. null clears it; omitted keeps it. | |
| value | Yes | The current value, as plain text: 1–120 characters, one line, none of [ ] < > * _ ~ ` | \ { }. Put units and qualifiers inside it when they change together, e.g. "500 MB" or "v2.4.1". On a blog in more than one language, keep words out of it ("500 MB", not "500 MB per user"): it shows the same in every language. | |
| blog_id | No | Your blog's id, as returned by signup. Optional with an API key: it defaults to the key's blog, and any id you pass must be that blog. Required when the server runs without API keys. | |
| dry_run | No | true writes nothing and returns every post and line the change would affect. Without it the change goes live on every post that uses the fact immediately. | |
| source_url | No | https URL the value was checked against. Not shown on pages. null clears it; omitted keeps it. | |
| confirmed_at | No | When you actually checked the value: an ISO 8601 date ("2026-10-21") or date-time with a time zone ("2026-10-21T09:30:00Z"). Not in the future, not before 2000. Defaults to now, so only omit it when you checked just now. | |
| expected_value | No | Compare-and-set: the value you believe is current (null: you believe the fact does not exist yet). If it differs, nothing changes and the call fails with FACT_CONFLICT carrying the current value. | |
| idempotency_key | No | Optional retry key, any unique string (e.g. a UUID). Retrying with the same key and identical arguments returns the first result instead of writing again; the same key with different arguments fails with IDEMPOTENCY_KEY_CONFLICT. Scoped to your API key and this tool. |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| fact | No | The fact as it is now (or would be, on a dry run). | |
| error | No | Present only on failure (isError: true). Success fields are absent then. | |
| changed | No | true when the value is new or different; false when only confirmed_at or the note moved. | |
| dry_run | No | true: nothing was written. | |
| rerendered | No | Published posts re-rendered by this call. | |
| affected_posts | No | Every post that uses the fact. Drafts are listed but not rendered. |