> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/help-center/ai-agents/my-agent-can-read-but-cannot-make-changes.md).

# My agent can read but cannot make changes

Restore write access when a connected agent can read Podigee but cannot change it.

The connection can read but cannot write when its grant lacks a required write scope, the user lacks resource access, or Podigee blocks writes for the account.

## Check the current grant

1. Run `get_me` and inspect `write_enabled` and `scopes`.
2. Run `doctor` with `check_write: true`.
3. Confirm that the target podcast belongs to the connected account.
4. Confirm that your Podigee user can make the same type of change.
5. Check whether the account or subscription has a reported write blocker.

A tool requires every scope that it lists. The write scopes are:

* `mcp:podcasts:write` for podcast, episode, bulk episode, and directory submission changes.
* `mcp:media:write` for upload sessions.
* `mcp:podcasts:write` and `mcp:media:write` together for publishing, import, and media production.
* `mcp:listeners:write` for listener changes. Feed protection changes through the guided feed-access flow also require `mcp:listeners:read` and `mcp:podcasts:write`.

## Add the required access

Reauthorize the connection. The client requests the permissions; review them on the consent screen before you approve. For a personal access token, create a new token with the missing permissions. An existing grant does not gain a new scope because the user asks for a different action in chat.

## Expected result

`get_me` reports write access, `doctor` reports no write blocker, and a dry run returns a change plan instead of an authorization error.

## If writes still fail

Do not retry the same mutation repeatedly. Send Podigee Support the tool name, target type and ID, time, granted scope names, and sanitized error. Do not send the token or confirmation value.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.podigee.com/help-center/ai-agents/my-agent-can-read-but-cannot-make-changes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.