io.usefulapi/edesk

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

4 of 18 tools are described as changing something (creating, editing, deleting, sending or running).

• edesk_whoamireads or searches

  “The eDesk user the API token belongs to: id, name, email, username, role and active flag.”

  Publisher declares: read-only yes · destructive no · open-world yes

  Takes no inputs.

• edesk_list_usersreads or searches

  “List the eDesk users (support agents) with id, name, email, username, role and active flag.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs

  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_list_channelsreads or searches

  “List the sales channels connected to eDesk (Amazon, eBay, Shopify, email, ...) with id, type, name, country and currency.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs

  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_list_tag_groupsreads or searches

  “List the tag groups that organize ticket tags.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs

  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_list_tagsreads or searches

  “List ticket tags with id, name, color, active flag and tag group id.”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs

  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_list_templatesreads or searches

  “List saved reply templates (id, name, subject, body text, channels, usage).”

  Publisher declares: read-only yes · destructive no · open-world yes

  2 inputs

  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_get_templatereads or searches

  “One reply template by id.”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • template_idintegerrequired“eDesk template id.”
• edesk_list_ticketsreads or searches

  “List support tickets from all channels with subject, type, status, channel, owner, contact, linked sales order id, tag ids, message ids, reply count and AI classification.”

  Publisher declares: read-only yes · destructive no · open-world yes

  13 inputs

  • statusstring“Only tickets with this status.”
  • typestring“Only tickets of this type.”
  • channel_idinteger“Only tickets on this channel (see edesk_list_channels).”
  • contact_idinteger“Only tickets of this contact (customer).”
  • owner_user_idinteger“Only tickets assigned to this user.”
  • sales_order_idinteger“Only tickets linked to this eDesk sales order id.”
  • seller_order_idstring“Only tickets for this marketplace order id (the id the marketplace shows).”
  • updated_afterstring“Only tickets last updated on or after this date, yyyy-mm-dd.”
  • updated_beforestring“Only tickets last updated on or before this date, yyyy-mm-dd.”
  • order_bystring“Sort field.”
  • order_directionstring“Sort direction.”
  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_get_ticketreads or searches

  “One ticket by id with its status, owner, tags, custom fields, linked sales order and the ids of its messages (read each with edesk_get_message).”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • ticket_idintegerrequired“eDesk ticket id.”
• edesk_get_messagereads or searches

  “One ticket message or internal note by id (from a ticket's message ids): body, direction, type (Message or Note), author and attachments.”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • message_idintegerrequired“eDesk message id.”
• edesk_list_contactsreads or searches

  “Search the contacts (customers) of the helpdesk by free text, email, name, phone number or consumer id.”

  Publisher declares: read-only yes · destructive no · open-world yes

  7 inputs

  • querystring“Free-text search.”
  • emailstring“Filter by email.”
  • namestring“Filter by full name.”
  • phone_numberstring“Filter by phone number.”
  • consumer_idinteger“Filter by consumer id.”
  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”
• edesk_list_sales_ordersreads or searches

  “List the marketplace/store orders that eDesk holds, with status, items, amounts, addresses, tracking codes and the linked ticket id.”

  Publisher declares: read-only yes · destructive no · open-world yes

  14 inputs

  • statusstring“Only orders with this status.”
  • channel_idinteger“Only orders from this channel.”
  • contact_idinteger“Only orders of this contact.”
  • seller_order_idstring“Only the order with this marketplace order id.”
  • id_frominteger“Only orders with an eDesk id greater than or equal to this.”
  • id_tointeger“Only orders with an eDesk id less than or equal to this.”
  • created_afterstring“Only orders created on or after this date, yyyy-mm-dd.”
  • created_beforestring“Only orders created on or before this date, yyyy-mm-dd.”
  • updated_afterstring“Only orders last updated on or after this date, yyyy-mm-dd.”
  • updated_beforestring“Only orders last updated on or before this date, yyyy-mm-dd.”
  • order_bystring“Sort field.”
  • order_directionstring“Sort direction.”
  • pageinteger“Page number, from 1 (default 1).”
  • items_per_pageinteger“Results per page, 1-100 (default 25).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.