Update to Tailwind

{
  "name": "tailwind-pinterest-scheduling",
  "description": "Create, schedule, and review Pinterest Pins through Tailwind. Use when the user wants to schedule Pins, pick a Pinterest Board, manage drafts, or check what is queued to publish.",
  "included_files": [],
  "skill_md_contents": "---\nname: tailwind-pinterest-scheduling\ndescription: Create, schedule, and review Pinterest Pins through Tailwind. Use when the user wants to schedule Pins, pick a Pinterest Board, manage drafts, or check what is queued to publish.\n---\n\n# Scheduling Pinterest Pins with Tailwind\n\nThe Tailwind MCP server creates and schedules Pinterest Pins on the user's\nbehalf. Each tool's own description covers its parameters. This file covers the\nthings the tools cannot tell you — the places where a correct-looking call still\nfails.\n\n## Start by resolving the account\n\nEvery tool takes an `accountId`, and it is Tailwind's numeric account ID, not a\nPinterest username or profile URL. Call `list_accounts` first and use an ID from\nthe response. If the user has more than one account and hasn't said which,\nask — publishing to the wrong Pinterest profile is not something you can undo\nfrom here.\n\n## Board IDs are where this usually goes wrong\n\nScheduling requires `boardId`, and it must be the **numeric board ID as a\nstring** — for example `\"1106196864631757445\"`. A Board name, a Pinterest URL,\nor a slug will be rejected.\n\nBoard IDs come from `list_boards`, which takes the account ID and returns each\nBoard's numeric ID and name. Call it rather than asking the user to find an ID\nby hand.\n\nThe same data is also published as a resource:\n\n```\ntailwind://accounts/<accountId>/boards\n```\n\nIf you read it that way, substitute the real account ID — the server advertises\nthe URI with a literal `{accountId}` placeholder, and reading that string\nverbatim will not return the user's Boards. `list_boards` needs no such care,\nwhich is why it is the better route.\n\n## Get the copy right before you create anything\n\nThere is no tool to edit a Pin once it exists. `schedule_post` changes only the\ntime and the Board; `create_post` always makes a *new* Pin. So a draft with the\nwrong title, description, media, or destination URL cannot be corrected through\nthese tools — the only route is `delete_post` and start again.\n\nConfirm the copy and the media with the user **before** calling `create_post`.\nDo not save a rough draft intending to refine it later.\n\nThe Board is the exception, and the one thing you can safely defer: `boardId`\ncan be supplied later when you call `schedule_post`.\n\n`create_post` without `sendAt` saves a draft, which is right when the timing is\nundecided but the content is settled. Adding `sendAt` schedules it, and makes\n`title`, `description`, `url`, and `boardId` all mandatory. `schedule_post`\nmoves an existing draft or queued Pin to a time and expects `title`,\n`description`, and `url` to already be set.\n\nAfter scheduling, confirm it landed with `list_posts` using `status: \"queued\"`\nrather than assuming success from the tool's response text.\n\n`sendAt` is ISO 8601 and must be in the future. Ask the user for their intended\ntime and time zone instead of inventing one.\n\n## Scheduling spends the user's credits\n\nMoving a Pin to scheduled consumes a Pin-scheduling credit from the user's plan.\nSaving a draft does not, and rescheduling an already-queued Pin is not charged\nagain.\n\nTwo consequences worth respecting: don't schedule speculatively to \"see if it\nworks\" — create a draft instead. And if a call comes back as a payment-required\nerror, that is a real billing outcome (out of credits, trial exhausted, or no\nplan access), not a transient failure to retry. Tell the user what happened\nrather than trying again.\n\n## When something fails\n\n- **Rejected board ID** — you almost certainly passed a name or URL. Call\n  `list_boards` and use an ID from the response.\n- **Missing required field on a scheduled Pin** — `title`, `description`, `url`,\n  and `boardId` are only required once `sendAt` is present. Either supply them or\n  save a draft instead.\n- **`delete_post` fails** — it only works on Pins that have not published yet.\n  Published Pins have to be removed from Pinterest directly.\n"
}