> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcitable.com/llms.txt
> Use this file to discover all available pages before exploring further.

# get_geo_priorities

> Returns the brand's top-priority recommendations from the Action Engine, ordered by time group.

Returns the brand's top-priority recommendations from the Citable Action Engine, ordered by time group (today → this-week → next-week → backlog). Each ticket includes a deep link back to the web app where the user can approve, edit, or dismiss the action.

## When to use

* "What should I do for AI visibility this week?"
* "What's the top priority for my brand?"
* "Give me my marketing to-do list."

Skip when the user wants visibility metrics (use `get_brand_visibility`) or posted-content performance (use `get_content_performance`).

## Inputs

| Field    | Type                                        | Default | Meaning                     |
| -------- | ------------------------------------------- | ------- | --------------------------- |
| `window` | `'today' \| 'week' \| 'next_week' \| 'all'` | `'all'` | Time horizon for the queue. |
| `limit`  | `int`                                       | `20`    | Page size.                  |

## Response

```
{ tickets: [...], totalRemaining, completed, effortRemainingMinutes, lastGeneratedAt }
```

Each ticket has `id`, `title`, `description[]`, `status`, `priority`, `effortMinutes`, `templateKey`, `deepLinkUrl`, `taskCategory`, `taskType`.

## Category taxonomy

`technical`, `content_creation`, `media_placement`, `content_optimization`, `opportunity`, `report`, `operational`, `generic`.

## Example

Calling with `{ window: "week", limit: 5 }` returns the five most urgent recommendations across today + this-week.

## See also

* [Overview](/mcp/overview)