Update to Nimble CRM

{
  "description": "Create or update contact custom fields, field tabs, groups, and choice options in Nimble. Use when the user asks to customize the contact field structure. Do not use for editing values on individual contacts.",
  "included_files": [],
  "name": "manage-contact-fields-in-nimble",
  "skill_md_contents": "---\nname: manage-contact-fields-in-nimble\ndescription: Create or update contact custom fields, field tabs, groups, and choice options in Nimble. Use when the user asks to customize the contact field structure. Do not use for editing values on individual contacts.\n---\n\n# Manage contact fields in Nimble\n\nUse the Nimble MCP connector as the source of truth.\n\n1. Call `get_contact_fields_structure` to inspect the current tabs, groups, fields, IDs, ordering, and `available_actions`.\n   Reuse existing structure when it fits the request; never guess IDs or logo values. If the user does not specify a\n   position, use the last existing sibling's ID as `insert_after` to append; use `null` only for an empty parent or when\n   placing the item first is intended.\n2. For a new tab, call `create_contact_field_tab` with the requested person/company contact types. For a new group, call\n   `create_contact_field_group` with its tab ID and a valid `logo_id` from an existing group; `\"1\"` is a known example.\n3. Call `create_custom_contact_field` with the target tab and optional group. A choice field needs\n   `field_type.values.ordering_type` and stable `{id, value}` options. Number and datetime fields need a matching\n   `presentation`. Read the returned structure for the new ID before subsequent changes.\n4. Use the corresponding update tools for existing tabs, groups, fields, and choice options. Updates change only supplied\n   properties. An explicit `null` for `insert_after` moves an item first; `group_id: null` removes a field from its group.\n   When moving a field to another tab, supply its destination `group_id` or `null` explicitly. Field type and multiplicity\n   cannot be changed by the update endpoint.\n5. To add or rename an option after creating a choice field, use `create_contact_field_choice` or\n   `update_contact_field_choice`.\n\nEach write returns the full current structure. Creating a tab, then a group, then a field is a sequence of separate\nwrites: if a later call fails, earlier changes remain. Check the returned structure before retrying an ambiguous failure.\nDo not create duplicate tabs, groups, fields, or options during retries. Writes require the account's Manage Custom Fields\npermission; report a permission error rather than attempting another route.\n"
}