> ## Documentation Index > Fetch the complete documentation index at: https://docs.attensira.com/llms.txt > Use this file to discover all available pages before exploring further. # The agent's tools > The tool groups an automation can be given, and the tools inside them that deliver work: reading the web, pull requests, articles, LinkedIn posts, Notion posts, community replies and client reports. These are the tools the Attensira agent itself uses inside a chat or an automation run. They are different from the [MCP tools](/mcp/tools), which are how your own assistant calls Attensira. ## Tool groups An automation's reach is set by **tool groups**, shown as "What it can look at" and "What it can change" on the automation's Configuration tab. A tool is available to a scheduled run only if the automation's allowlist includes its group. The groups that deliver work: | Group | Tools | What it can change | | ------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- | | Your own data | Readings, pages, deciding sources, `win_plan`, the business profile, and (when a Notion blog is mapped) `list_blog_posts`, `read_blog_post` | Nothing | | The open web | `web_search`, `web_fetch` | Nothing | | Your site's code on GitHub | `list_repo_files`, `read_repo_file`, `search_repo_code`, `resolve_url_to_file`, `propose_fix` | Opens a pull request | | Make things | `write_document`, `read_document`, `draft_social_post`, `generate_image`, `write_skill` | Files an article or post for your approval | | Rewrite a passage on your site | `propose_edit` | Files a before/after. Publishes nothing | | Update a post on your Notion blog | `propose_blog_update` | Files a before/after of a Notion post | | Find who to contact | `find_outreach_targets`, `find_contact`, `draft_outreach` | Files an email draft. Never sends | | Answer questions where people already argue | `find_community_threads`, `propose_community_answer` | Files a reply draft. Never posts | | Get listed on directories | `propose_listing` | Files a prefilled listing. Never submits | | Publish the client report (`reports`) | `publish_client_report` | Publishes a [client report](/agencies/client-reports) | A connected plugin, such as Notion, is its own group named after the plugin. If a scheduled run needs an integration that the automation's tool list does not include, nothing is added to your Inbox, because connecting it would not help that run. It is recorded on the run's transcript instead. To fix it, add the tool's group to the automation. ## Reading the web **`web_fetch`** reads one page. **`find_contact`** reads the pages of a site to find who runs it. Both, and the refresh of your site's page map, go through our web reader. * Each open-web read is metered in credits. See [Credits](/account/credits). * `web_fetch` reads Reddit threads free of charge, and returns the post, the top comments, whether the thread still takes replies, and the subreddit's rules. * When the web reader is unavailable, reads fall back to a plain HTTP fetch with **no JavaScript rendering**. Pages built entirely in JavaScript may come back empty then, and the agent says so instead of guessing what the page says. **`find_community_threads`** lists the community threads (Reddit, Hacker News, Stack Overflow and Stack Exchange, Quora) that answers to your tracked prompts cite. It is free and read-only. See [Community answers](/agent/community-answers). ## Pull requests **`resolve_url_to_file`** finds the file behind a URL in your connected repositories. It also reports where the page's title and description are defined, and where a new page at that URL would go. **`propose_fix`** proposes a change to a file as a pull request (see [GitHub](/agent/github)). * Proposing a path that does not exist creates a **new file**, such as a new post under a content root. * `prompt_ids` (optional) names the tracked prompts the change is meant to move. Those are the prompts [re-read after it ships](/measure/before-and-after). Without them no before-and-after is measured. ## Articles and posts **`write_document`** writes an article. It also appears as a work item under [Work → To approve](/agent/inbox#written-for-you) and as a draft on the content plan. Where it goes on approval depends on what is connected: 1. A connected GitHub repository with a blog directory: approving opens a pull request that adds the post as a new file, with front matter that follows your existing posts. 2. A mapped [Notion blog](/agent/notion): approving sends it to Notion as a draft page. 3. Otherwise, a copy handoff: you paste it into your site and [mark it shipped](/agent/inbox#mark-shipped) with the live URL. Articles always wait for a person's yes, in every mode. Revising an article that is still waiting updates the same work item. Briefs, emails and notes the agent writes are not filed as work. **`draft_social_post`** leaves a **LinkedIn post** in Work, ready to copy. Attensira never posts to LinkedIn: you post it from your own account and mark it shipped with the post's link. The post always carries the link to its source page. ## Notion posts **`list_blog_posts`** and **`read_blog_post`** list and read the posts in your mapped Notion blog. **`propose_blog_update`** proposes a new version of one as a before/after. All three are offered only when a Notion blog database is mapped. See [Notion blog](/agent/notion). ## Client reports **`publish_client_report`** publishes the [client report](/agencies/client-reports) for the period that just ended. It runs only when the automation's allowlist includes **Publish the client report**. The agent writes only the words (summary, highlights, next period, notes); every number on the report is read from the workspace's data for the closed period. ## House skills The agent follows written procedures for recurring jobs, called house skills. Among them: | Skill | Used by | | ---------------------------- | --------------------------------------------------------------------------------- | | `orchestrate/daily-win-plan` | The [Daily win plan](/agent/autopilot#the-daily-win-plan) and the Event responder | | `report/client-weekly` | The Weekly client report | | `report/client-monthly` | The Monthly client report | | `report/client-quarterly` | The Quarterly client review |