# alldone.team

> AI tools for stories and videos (Story Builder), job search and applications (Judy Job) and property investment calculations (Property Screener).

## Use the tools as an AI agent

alldone.team tools (Story Builder, Judy Job, Property Screener) can be used by AI agents from any signed-in alldone.team tab: window.alldoneTeam (help(), listTools(), callTool(name, args)) or native WebMCP tools. No MCP connector is needed in the browser; every call runs as the signed-in user with the same tools, permissions and credit costs as https://alldone.team/mcp.

Use the first route that can do the task, in this order:
1. Connected alldone.team MCP: if a connection to https://alldone.team/mcp is already installed and offers the needed tools, use it directly. Do not confuse it with an unrelated Alldone productivity/task MCP. If it is missing, continue with the browser routes; never require installing a connector first.
2. Built-in WebMCP: open the alldone.team page in the authorized built-in/in-app browser (even if it is already open in another browser) and use its native WebMCP tools, starting with alldone_team_context.
3. Built-in JavaScript: if built-in WebMCP is unavailable or cannot do the task and page JavaScript is permitted there, use await window.alldoneTeam.help(), listTools() and callTool(name, args).
4. External WebMCP: only if both built-in routes cannot do the task, open the same page in an authorized external browser (for example Chrome) and use its native tools, starting with alldone_team_context.
5. External JavaScript: if external WebMCP cannot do the task, use window.alldoneTeam in that browser when page JavaScript is permitted.
6. Built-in Commands, then external Commands (last resort): only on a product page; follow that product's guide (its Commands panel, connect=browser&commands=1).

In the browser, the page also carries a JSON manifest in `<script type="application/json" id="alldone-agent-api">`. If the user is not signed in, `window.alldoneTeam.state` is `signed_out` and `context().signInUrl` names the sign-in page: ask the user to sign in; the page comes back to where it was.
alldone.app users get these tools in Anna Alldone without any setup.

## Rules

- Use the first route that can do the task, in this order: Connected alldone.team MCP → built-in WebMCP → built-in JavaScript → external WebMCP → external JavaScript → built-in Commands → external Commands. Do not ask the user to add a connector first.
- Read the user's request, then await window.alldoneTeam.listTools() (or the native tool list) and call the matching tool. Start a product with its *_capabilities or *_context tool, which returns its workflow.
- Tools that cost credits name their cost. Confirm a paid or consequential action with the user before calling it, unless they already asked for exactly that action.
- Never read, copy or send authentication tokens, cookies or browser storage. Sign-in and Google consent are always done by the user.
- UI-only tools (opening a view, editing an open form, importing a local file) exist only on the product's own page through its page helper; open that page when you need them.

## Products

- [Story Builder](https://alldone.team/story-builder-agents.txt): page https://alldone.team/connor-consultant/story-builder; UI tools there through window.alldoneStoryBuilder.
- [Judy Job](https://alldone.team/judy-job-agents.txt): page https://alldone.team/judy-job/job-radar; UI tools there through window.alldoneJudy.
- [Property Screener](https://alldone.team/property-screener-agents.txt): page https://alldone.team/ricky-returns/check-investment-opportunity; UI tools there through window.alldonePropertyScreener.