Skip to main content
Nine tools. Eight of them only read — the ninth is the one that runs a bulk update.

​
Reading

describe_database is what lets Claude hold a sensible conversation rather than interrogating you. Give it a database and it already knows which properties exist, what values they take, and what templates are available.

​
Running

This is the only tool that changes anything. It spends one credit per page.By default it adds the template to each page and leaves the existing content in place — unlike the console, which clears the page first. Ask for clearing explicitly if that is what you want, and know that it cannot be undone.It will not run from a bare instruction either — it needs a selection you have previewed and a count you have been shown. See What to watch for.

​
How a run actually goes

1

Claude finds the database

search_databases, then describe_database for the details.
2

It proposes a condition

Built from the properties that actually exist, not guessed.
3

It previews

preview_selection returns the count, the credits it will cost, and a few example page titles — so you can tell whether it caught what you meant.
4

You agree

Nothing runs before this.
5

It runs and follows the job

start_bulk_update, then get_job until it finishes.

​
Selecting specific pages

Conditions are the way to target a lot of pages. For a specific handful, name them and Claude will pass those instead — up to 100 that way. Past that, a condition is both easier and more reliable.

​
Next

What to watch for

Credits, irreversibility, and the guards that stop surprises.

Credits and plans

What a run costs.