Use AI to organize links and campaigns

Use a read, propose, confirm pattern

For changes, ask the AI client to inspect the current state first, propose the exact mutation, and wait for your confirmation. This keeps names, IDs, dates, tags, UTM values, and destination URLs visible before a write tool runs.

A confirmation in chat is your operating instruction. It does not replace SimpURL ownership checks, plan limits, scope checks, or client approval controls.

Create links and organize tags

1. 1Create a link: "List my recent links first. Then propose a new link for https://example.com/launch with title Launch page, tags launch and q3, and no expiration. Wait for my confirmation before creating it."
2. 2Create a namespaced link: "Find my available namespaces, propose the best match for https://example.com/docs, and show the destination, title, namespace, tags, and slug before asking me to confirm."
3. 3Apply tags: "Find links containing example.com and show their current tags. Propose replacing their tags with docs and evergreen, grouped by link ID. Wait for confirmation before updating tags."
4. 4Avoid duplicate creation: "Before creating a link, search for an existing link with the same destination. If one exists, show it and ask whether to reuse it; do not create a duplicate without confirmation."

• The link write tools honor SimpURL quotas, namespace and campaign ownership, tag limits, expiration rules, and duplicate behavior on the server.
• The current MCP catalog supports up to 10 tags in the list-links and update-tags inputs, and up to 10 tags on a campaign.

Create campaigns and UTM settings

1. 1Inspect first: "List my campaigns and summarize each campaign's dates, status, tags, UTM parameters, and mapped-link count."
2. 2Propose a campaign: "Draft a campaign named Spring launch for next month. Suggest exact start and end dates in my local timezone, with tags spring and launch and UTM source newsletter, medium email, campaign spring-launch. Show the dates, timezone, and exact values, then wait for my confirmation before saving."
3. 3Assign links: "Find links tagged spring that are not assigned to a campaign. Propose assigning them to the Spring launch campaign by link ID, then wait for confirmation."
4. 4Update safely: "Show the current campaign before changing it. Propose only the requested field changes and ask me to confirm the campaign ID and final values."

Manage namespaces and domain mappings

1. 1Inspect first: "List my namespaces and domain mappings, including which mappings point to each namespace."
2. 2Create a namespace: "Propose a namespace named docs. Check the current namespace limit and existing names, then wait for confirmation before creating it."
3. 3Map a domain: "Propose mapping destination domain example.com to namespace docs. Show the namespace ID, normalized domain pattern, and any existing mapping conflict. Wait for confirmation before setting it."
4. 4Remove safely: "Find the mapping for example.com and show its ID and namespace. Do not remove it until I confirm the exact mapping ID."
5. 5Remember that a namespace can be renamed or deleted only when the server's ownership and unused-namespace rules allow it.

Request analytics reports

1. 1Account report: "Get my SimpURL analytics summary for the last 30 days. Include total clicks, top sources, browsers, operating systems, time of day in UTC, popular links, and whether the result was truncated."
2. 2Campaign report: "List campaigns, then get campaign analytics for campaign ID <id> for 30 days. Summarize performance and link results without exposing raw visitor identifiers."
3. 3Comparison: "Read the current report for campaign ID <id> for 30 days, compare it with the previous period if supported, and label the comparison window and data limitations."
4. 4Use a range of 7, 14, 30, 90, or 180 days. Ask the client to report the plan cap instead of silently retrying a longer range.

• The MCP analytics tools return aggregated data; raw IP addresses and raw user-agent strings are omitted from the compact report.
• Analytics are not a 1:1 copy of a social or ad platform dashboard. Browser privacy settings, blocked referrers, preview crawlers, redirects, attribution windows, and platform counting rules can produce different totals.
• If the client reports too many requests, wait and retry once rather than allowing it to repeat the request in a loop.