Changelog

- Add a subscriber to a group
+ Add a subscriber to a group.
+ If no subscriber matches the ID/email or no group matches the ID, this returns a normal (non-error) result with found: false rather than failing — a missing subscriber or group is an expected outcome, not a tool error.

  Delete a subscriber from the account.
+ If no subscriber matches the ID, this returns a normal (non-error) result with success: false rather than failing — a missing subscriber is an expected outcome, not a tool error.

  Fetch the full record for a single MailerLite resource using an identifier returned by the search tool.
+ Always call search first to obtain this id — never guess or fabricate one.
  Args:
- - id (string, required): A prefixed identifier from search results formatted "<kind>:<id>" where kind is campaign, group, form, or automation (e.g.
+ - id (string, required): A prefixed identifier from search results formatted "<kind>:<id>" where kind is campaign, group, form, automation, or segment (e.g.
  "campaign:123").
+ Alternatively, a bare id (no prefix) if "type" is also given.
+ - type (string, optional): One of campaign, group, form, automation, segment.
+ Required only when "id" is a bare id without a "<kind>:" prefix.
  Returns: { "id": string, "title": string, "text": string, "url": string, "metadata": object }.
  "text" is the full resource serialized as JSON; "metadata" carries kind-specific summary fields (e.g. status/type for campaigns, active_count for groups).
  Examples:
  - After search returns "automation:012" -> fetch with id="automation:012".
- - The id must include the kind prefix from search; a bare numeric id or an unsupported kind returns an error.
+ - If you already have a bare numeric id and know its kind -> fetch with id="123", type="group".
+ - An id without a "<kind>:" prefix and no "type" argument, an unsupported kind, or an id that matches nothing returns an actionable error telling you to call search first.

- Get details of a specific campaign
+ Get details of a specific campaign.
+ If no campaign matches the ID, this returns a normal (non-error) result with found: false rather than failing — a missing campaign is an expected outcome, not a tool error.

  Get subscribers in a specific group.
  Results are cursor-paginated — pass the cursor from the previous response to fetch the next page.
+ If no group matches the ID, this returns a normal (non-error) result with found: false rather than failing — a missing group is an expected outcome, not a tool error.

- Get activity history for a subscriber (opens, clicks, etc.)
+ Get activity history for a subscriber (opens, clicks, etc.).
+ If no subscriber matches the ID or email, this returns a normal (non-error) result with found: false rather than failing — a missing subscriber is an expected outcome, not a tool error.

- Search across MailerLite campaigns, groups, forms, and automations by free-text query, matching names and key fields (subject, type, status, slug).
+ Search across MailerLite campaigns, groups, forms, automations, and segments by free-text query, matching names and key fields (subject, type, status, slug).
  This is a discovery tool that returns lightweight result stubs, not full records.
  To get the full details of a result, pass its id to the fetch tool.
+ Always call search before fetch — fetch requires an id from these results (or a bare id plus an explicit type; see the fetch tool description).
  Args:
  - query (string, required): Case-insensitive text to match across resource names and fields.
  - limit (number): Max results, 1-20 (default 10).
  Returns: { "results": [{ "id": string, "title": string, "url": string }] }.
- Each id is a prefixed identifier like "campaign:123", "group:456", "form:789", or "automation:012" — pass it verbatim to fetch.
+ Each id is a prefixed identifier like "campaign:123", "group:456", "form:789", "automation:012", or "segment:345" — pass it verbatim to fetch.
  Returns an empty results array (never an error) when nothing matches.
  Examples:
  - "find my black friday campaign" -> query="black friday"
  - "which welcome automation do I have" -> query="welcome"
  - For unfiltered listing use list_campaigns / list_automations / list_resources instead.