Timothe's Growth Calendar
Plan, schedule and generate SEO articles on a content calendar.
Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeCan modify data
What it can do
- Get Credits: Check how many credits this workspace has left and whether it is on a paid plan. Call this before starting anything that spends credits, so you can tell the user whether it will go throug
- List Tracks: List every content track in this workspace with its cluster, market (language plus country), timezone, how many articles are still pending, and whether it is active or completed. Start he
- Get Calendar: Read one month of the calendar across all tracks: planned articles, scheduled notes, and the articles already generated. Use this to see what is scheduled before changing anything.
What data it sees
Do you need an account
No: the server works without sign-in
Plan, schedule and generate SEO articles on a content calendar.
Ask your agent to show what is scheduled this month, plan a topic cluster, move or retitle a planned article, or write one now. Article generation runs unattended on its publish date, so the calendar keeps working after you close the terminal.
Server tool list (13)
Raw names from tools/list. Only developers need these.
| get_credits | Check how many credits this workspace has left and whether it is on a paid plan. Call this before starting anything that spends credits, so you can tell the user whether it will go through instead of letting it fail. |
| list_tracks | List every content track in this workspace with its cluster, market (language plus country), timezone, how many articles are still pending, and whether it is active or completed. Start here to see what exists. |
| get_calendar | Read one month of the calendar across all tracks: planned articles, scheduled notes, and the articles already generated. Use this to see what is scheduled before changing anything. |
| read_article | Read one generated article's editable source for a given track and date. Line 1 is "revision: N" (pass N to edit_article as expectedRevision); after a blank line follows the source document: a frontmatter with the editable fields (title, description, slug, note), then the article's markdown body. edit_article matches replacement strings against exactly this source text. |
| get_writing_style | Read the workspace's writing-style guidance, which every generated article follows. Read this before proposing style changes. |
| get_cluster_context | Read the current topic cluster and its subject-matter context for one track, plus the dates that still expect an article. |
| get_run | Check a run started by plan_cluster or generate_article. Those take several minutes, so poll this until the status is no longer pending or running. |
| create_note | Add a dated reminder note to the calendar. The note is emailed to the owner on its date. Use this for things to do, not for articles to write. |
| update_plan_item | Edit one planned (not yet generated) article: its title, type, length, writer guidance, URL slug, or the day and time it is scheduled for. Rejects dates that already have an article or lie in the past. |
| edit_article | Edit one GENERATED article with exact string replacements, applied in order to the source returned by read_article. Each oldString must appear exactly once unless replaceAll is true; include surrounding context to disambiguate. The frontmatter fields (title, description, slug, note) are edited the same way as the body, and deleting an optional frontmatter line clears that field. Do not touch image lines or gcimg: placeholders. Call read_article first and pass its revision as expectedRevision; on a revision conflict or a failed match, read again and rebuild the edits. The result is re-linted and saved atomically, or not at all. |
| delete_plan_item | Delete one planned article and its scheduled reservation, freeing that day. Does not affect articles that were already generated. |
| plan_cluster | Costs 200 credits and requires a paid plan. Plants one finite topic cluster onto the calendar: researches the topic, then creates a planned article plus a scheduled reservation for each publish date. Takes several minutes; returns a run id to poll with get_run. Requires paid plan. |
| generate_article | Costs 600 credits and requires a paid plan. Writes the planned article for one track and date now, instead of waiting for its scheduled reservation. Takes several minutes; returns a run id to poll with get_run. |